Website Error Log.
  https://agius.co 

This page lists the last few HTTP errors on this website.
  Date/Time = The website date and time someone tried to load the page. 
  IP address = The IP address of the user trying to load the page. 
  Page URL = The address of the page that could not be loaded. 
  Status = The HTTP status codes. (See list below) 
Note:
The following URL's would not load on the listed error date, but may have been OK before and/or after this date.
 Date:  Time:  IP address:  Page URL:  Status:
9/06/2026 9:18am  45.198.224.188  http://213.155.2.230:80/index.htm  404 
9/06/2026 8:07am  52.167.144.195  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WGX2F7XCF-7ZQ2S70-1M91WYSM7QWBGO  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RUIZGWM1C0UA0I6NZ8W91EVF2G911QOR  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BUD-_JFK97MAIJN149KMFC6UU0I2D3PN  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LKA3UQVPUH41WGSS5CJXIFWMP_QIXK_W  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E7GDXKQDRHCG9KR-BTFMMZZF1611O3QX  404 
9/06/2026 8:01am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/J7Y1Z58UWCGAUF-OTTAQ2E-U2UZ90EZX  404 
9/06/2026 8:01am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/2BZGKYM9Y6G25QXCCL9CL4GUFWW-UFQF  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HT1VJ5H56-8DZ6A3W3BFPOM-3MFJ_LFN  404 
9/06/2026 8:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1R0YG3TOSVO2XFUMKQQWU71-TM1PNRQV  404 
9/06/2026 6:18am  47.128.60.162  https://agius.co/robots.txt  403 
9/06/2026 5:59am  45.205.1.198  http://213.155.2.230:80/index.htm  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/254_ZYLA6OLR7TOIS6-KL7740OUPIHQI  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/A-1P-0SPUSNV5N1YA4FC7VXWCK28IAS_  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1EM_WCWE74DXHNBFX1GP8Q-OWXSAWB_3  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T6T-ON6PDQEPX_X-_S4LNJ7MWX9D53RG  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RQQC4SUMI_E73ZFRM2PH92N5PZZN0N19  404 
9/06/2026 5:01am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/SGLDB38YM51T4FXV9NI-Q9AU7HLBU69Y  404 
9/06/2026 5:01am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/3-9KO2CS0BHR9DSW5-DIQ_AVT5PC5QEY  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/OK6YW0VIRK11RZPTJF366SPCOZ_H26ET  404 
9/06/2026 5:01am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-XYQ6IWAGNCAP2JXHP5AYB1ZE4KQ9_YX  404 
9/06/2026 4:20am  20.237.160.172  http://213.155.2.230/mcp  404 
9/06/2026 4:05am  34.87.98.241  https://agius.co/wordpress/  404 
9/06/2026 2:14am  14.233.247.41  https://agius.co/os/files/..%5Cindex.php  404 
9/06/2026 2:04am  34.96.45.144  https://agius.co/ads.txt  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/05ILW9UVDAEL8GU1ORLZ0RQ0N3H4K4FZ  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NYFXA3BO1DG7CHU2QMU1Z-PAB16X1GPS  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/M0V06OMS458H51E7-EKE-FRVHHGCHXUQ  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MI2O0-TIETU_L8RKT5DILEG05FOYH_B-  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_I8J9VDEA8SJMJZMSLOWJ84NH2JM5481  404 
9/06/2026 2:02am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/5XTBVZ-NI1VT-SQSYN-1Z3L_DM-9PWGP  404 
9/06/2026 2:02am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/NZQFT8G1OQ9K8CFWUINIINUPYHI4I6-N  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T3-UL4S4KLNFNQ_CPBV5IIB6IBNF3W7O  404 
9/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/53QAEO5AIDYWCO8II_4PJKI2OTA_RDZV  404 
8/06/2026 11:39pm  31.56.209.222  http://213.155.2.230:80/boaform/admin/formLogin  404 
8/06/2026 11:35pm  5.61.209.96  http://213.155.2.230:80/SDK/webLanguage  404 
8/06/2026 11:12pm  38.12.32.3  http://213.155.2.230/cgi-bin/login.cgi?username=eurek%20eurek  404 
8/06/2026 11:12pm  38.12.32.3  http://213.155.2.230/cgi-bin/login.cgi?username=eurek&password=eurek  404 
8/06/2026 11:02pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SFOQ9M-2L7RLTT7G1FGI5GESF7YIH4_B  404 
Note: Only the last 40 records are displayed here.

    HTTP status number list:
    Only some of the following are error and recorded on this website.
  • HTTP 100 = Continue. Server received request headers, and client should proceed to send the request body.
  • HTTP 101 = Switching protocols. Requester asked server to switch protocols and the server is acknowledging it.
  • HTTP 102 = Processing. The server has received and is processing the request, but no response is available yet.
  • HTTP 103 = Checkpoint. This code is used in the resumable HTTP requests. Resume/aborted PUT or POST request.
  • HTTP 122 = Request-URI too long. IE7-only code allows a maximum of 2083 characters.
  • HTTP 200 = Requested document has been processed and sent to you.
  • HTTP 201 = Created. Request fulfilled and a new resource is being created.
  • HTTP 202 = Accepted. Request has been accepted, but processing has not been completed.
  • HTTP 203 = Non-authoritative information. Server processed the request, but is returning information that may be from another source.
  • HTTP 204 = No content. Server successfully processed the request, but is not returning any content.
  • HTTP 205 = Reset content. Same as 204 response, but also requester reset of the document view.
  • HTTP 206 = Partial content. Server delivering only part of resource due to a range header sent by client.
  • HTTP 207 = Multi-status. Message body that follows is an XML message.
  • HTTP 226 = IM used. The server has fulfilled a GET request for the resource.
  • HTTP 300 = Multiple choices. The client may follow a number of different choices.
  • HTTP 301 = The document or directory has been moved permanently.
  • HTTP 302 = Found. Server received data and the redirect should be issued with a separate GET message.
  • HTTP 303 = Redirect web applications. Server received data and the redirect should be issued with a separate GET message.
  • HTTP 304 = Not modified. The resource has not been modified since last requested.
  • HTTP 305 = Use proxy.
  • HTTP 306 = Switch proxy.
  • HTTP 307 = Temporary redirect. The request should be repeated with another URI.
  • HTTP 308 = Resume Incomplete.
  • HTTP 400 = A bad HTTP request was sent from your browser to the website.
  • HTTP 401 = Unauthorised. You may have entered an invalid password.
  • HTTP 402 = Payment required to view the file or directory.
  • HTTP 403 = Forbidden. You do not have permission to view the page.
  • HTTP 404 = The file or directory was not found.
  • HTTP 405 = Method not allowed. EG. Using Get and not Post.
  • HTTP 406 = Not acceptable. Requested resource is only capable of generating content.
  • HTTP 407 = Proxy authentication required.
  • HTTP 408 = Request timeout. Server timed out waiting for the request.
  • HTTP 409 = Conflict. Request could not be processed because of conflict in the request.
  • HTTP 410 = Gone. The resource requested is no longer available and will not be available again.
  • HTTP 411 = Length required.
  • HTTP 412 = Precondition failed. The server does not meet one of the preconditions request.
  • HTTP 413 = Request entity too large. The request is larger than the server can process.
  • HTTP 414 = Request-URI is too long.
  • HTTP 415 = Unsupported media type.
  • HTTP 416 = Requested range not satisfiable. Request for portion of file that server cannot supply.
  • HTTP 417 = Expectation failed. The server cannot meet the requirements of the expect request-header.
  • HTTP 418 = I'm a teapot. This code was defined in 1998 as one of the traditional.
  • HTTP 422 = Unprocessable Entity. The request was correct but was unable to be followed due to semantic errors.
  • HTTP 423 = Locked. The resource that is being accessed is locked.
  • HTTP 424 = Failed Dependency. The request failed due to failure of a previous request.
  • HTTP 425 = Unordered Collection.
  • HTTP 426 = Upgrade required. Should switch to a different protocol.
  • HTTP 444 = No response. Nginx HTTP server extension.
  • HTTP 449 = Retry with a Microsoft extension. (Windows Parental Controls are turned on)
  • HTTP 450 = Blocked by Windows parental controls. (Windows Parental Controls are turned on)
  • HTTP 499 = Client closed request. Nginx HTTP server extension.
  • HTTP 500 = Internal Server Error. Could be bad script code, invalid .htaccess file, etc.
  • HTTP 501 = Not Implemented. Server dose not recognise the request method, or can not fulfill the request.
  • HTTP 502 = Bad Gateway. The server received an invalid response from the upstream server.
  • HTTP 503 = Service unavailable. Could be due to too much traffic for server.
  • HTTP 504 = Gateway timeout. Could be due to too much traffic for server.
  • HTTP 505 = HTTP Version not supported by website server.
  • HTTP 506 = Variant negotiates.
  • HTTP 507 = Insufficient Storage on webdite server.
  • HTTP 509 = Bandwidth Limit Exceeded for website.
  • HTTP 510 = Not Extended.
This page was last updated on;
9/06/2026 - 10:21am GMT / UTC