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:
10/07/2026 5:22pm  66.249.69.96  https://agius.co/ads.txt  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/X3TG4Q9RS6NVO9G7INOL2M362TY0RHL8  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/30IE34SH7044M67E6TPOWV75OHGL4OGU  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UKJW2F_YMYAKFO5DXIX3IU74XT57ED23  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3YBDEXEUSVD7J-EU7DZ6QWSJN3W3KF63  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SJ3-U2UI58_GHT040GCWAFK0R7WVJPR0  404 
10/07/2026 5:18pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/U7WIU5KKL4G5V0RQ6NZ8W0TUDYZ0AKFD  404 
10/07/2026 5:18pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/G0XEP4KKS_E_21786OJZB1A4SJIX_EB8  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UJFYEPA5OJSSR1ZNEURD79JS9N-V0534  404 
10/07/2026 5:18pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NHUZ-76GE4K3N60AAY3V01L1T8DKJKCT  404 
10/07/2026 4:20pm  156.59.198.135  https://agius.co/WindowsLogos/Windows95.png  403 
10/07/2026 4:10pm  2.124.182.200  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
10/07/2026 3:57pm  54.91.122.193  https://swiftdomainhosting.com/  403 
10/07/2026 3:35pm  47.128.60.126  https://agius.co/robots.txt  403 
10/07/2026 3:26pm  156.59.198.135  https://agius.co/415.shtml  403 
10/07/2026 2:44pm  20.64.105.25  http://213.155.2.230/developmentserver/metadatauploader  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Y3VZ_ZAKMX61SIKMO387X-HL39DRDISL  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/YKSDJ1XHV26WIUIRWOV6QX0H3AHN_M_K  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2QRQP7GKAVVPT2NF1X8IF1BM28Z5GE2M  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2JRZI059RJQ52FBC81RI70CMD4SE-L87  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P9TRMDMIOENXF9HD8W65URJH29O3PW3I  404 
10/07/2026 2:22pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/DOG4V4LY8V0Z9Q-X286J3FVMV9CFEY6C  404 
10/07/2026 2:22pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/P3B9EVCC52_2AVT5N0W5GOUBKPYP8186  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/EXMTHYJCPCKUOSK1KYVWIPGHJ8ZWYKC6  404 
10/07/2026 2:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4RY9BI244ZZ9NAS4QWQR9ROVK_MXGCC0  404 
10/07/2026 2:10pm  156.59.198.135  https://agius.co/http-error.php  403 
10/07/2026 1:50pm  186.18.108.105  https://agius.co/os/files/..%5Cindex.php  404 
10/07/2026 11:56am  20.221.71.226  https://213.155.2.230/owa/auth/logon.aspx  404 
10/07/2026 11:27am  69.5.169.11  https://213.155.2.230/sse  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QZJNM0G0ILHBUSECNKGJWAH-PI8ZETHJ  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/44RSWD4OY33XRAOJTDDGGURWY2-UO4NG  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/YD7IHSAVSKF8R7WQOEMKO0SHOL54NQOT  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QK21GX5G89KSV0Z144CFH0G78VO0XAKZ  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WN3PN9E5S52ETDBME3J7VZZIN7DGX-MD  404 
10/07/2026 11:19am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/48PN2IA8KWNBFUZVNSL7Q91ZS9ZKK6NW  404 
10/07/2026 11:19am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/WDUIG6K4VY11F6Y5GBAW2FG-N25H34SZ  404 
10/07/2026 11:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7PS3ZAPITVRIZLZNSKNDZHC8HFBE2EPS  404 
10/07/2026 9:53am  47.128.60.158  https://agius.co/http-error.php  403 
10/07/2026 8:42am  66.132.172.184  https://213.155.2.230/wf1urhdr_kx4  404 
10/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HUCI2TZBODWO00W6-5O_IJJ1WVT6D9_H  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;
10/07/2026 - 6:02pm GMT / UTC