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:
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/82JM5XD2RYOQ9Y_CK66YCIRGFEAZA_2Z  404 
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UXNUAYEQGKVIZPC2ZQ2KPGGU3SS6YITL  404 
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I8D7J_8OKYA_VKUBDPEMZY21CLJ_LJDY  404 
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PHNF182LP4H1DZ6MUN3_VC9HHJ9TUV-W  404 
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_F1FAJ3UNAH61Y9JA5BZ2R2ABBVHNTTA  404 
12/07/2026 8:23pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/84NHA0WK2L6KWMDYWZ72-O5ZU4D6GBRK  404 
12/07/2026 8:23pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/OFIR089BLMF16DW-PITWUL7QBS5_8IIG  404 
12/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JSLM6D5KKMR1EVL5O4ATC5Q0QE4H0GQ5  404 
12/07/2026 8:13pm  52.167.144.197  http://http.agius.co/sitemap.xml.gz  404 
12/07/2026 8:13pm  20.65.193.168  https://213.155.2.230/owa/auth/logon.aspx  404 
12/07/2026 8:06pm  66.132.172.102  https://213.155.2.230/sitemap.xml  404 
12/07/2026 6:42pm  85.208.96.194  https://agius.co/webwindow/history/WebWindow.exe  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/595I5I_M7R7EACK7M933QDROGR71MCI7  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/S8G8H73_DY-UX5HU0HT9MAUUUF8PX6-R  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_GSOJBT_SST2PDXTH1DQCJJCIENY-UXB  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-O3RL_MVVOZG6CUYQ5CYGG97-90N8YZV  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2R-_KM0TVG96IQP6FP6DOQTA5WW8CSZ5  404 
12/07/2026 5:23pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/A4QBZJ43S-R6XWMWKPKO8GUAV7U_2UN6  404 
12/07/2026 5:23pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/9DW11RX9HWHMYDLJGR3L65PHL14FD0OQ  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LMWWMUQ5UPY6D3P_VPIX1I5RQ93MWZY8  404 
12/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RAK2QVWJ2S89RUSWTYY0IDFDHT8XR-3P  404 
12/07/2026 5:22pm  66.249.69.96  https://agius.co/ads.txt  404 
12/07/2026 4:12pm  74.125.213.42  https://agius.co/.well-known/traffic-advice  404 
12/07/2026 3:46pm  216.73.216.110  https://agius.co/webwindow/history/file:///C:/Windows/Media/tada.wav  404 
12/07/2026 3:40pm  147.185.132.78  http://mail.swiftdomainhosting.com/.well-known/security.txt  404 
12/07/2026 3:36pm  114.119.157.245  https://www.agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
12/07/2026 3:34pm  147.185.132.147  https://213.155.2.230:443/.well-known/security.txt  404 
12/07/2026 3:03pm  47.128.32.116  http://swiftdomainhosting.com/robots.txt  403 
12/07/2026 2:55pm  47.128.32.191  https://swiftdomainhosting.com/robots.txt  403 
12/07/2026 2:55pm  156.59.198.136  https://swiftdomainhosting.com/files/Agius_CoatOfArms_005.png  403 
12/07/2026 2:54pm  141.98.11.134  http://swiftdomainhosting.com/sftp-config.json  404 
12/07/2026 2:54pm  141.98.11.134  http://swiftdomainhosting.com/.vscode/sftp.json  404 
12/07/2026 2:04pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
12/07/2026 12:39pm  2.124.182.200  https://agius.co/stpauls/pages/images/fonts/NouveauFLFExtra.ttf  404 
12/07/2026 12:39pm  2.124.182.200  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
12/07/2026 12:32pm  188.166.145.217  https://213.155.2.230/.well-known/security.txt  404 
12/07/2026 12:32pm  206.189.22.47  http://213.155.2.230/security.txt  404 
12/07/2026 12:32pm  206.189.22.47  http://213.155.2.230/.well-known/security.txt  404 
12/07/2026 12:26pm  143.137.166.223  http://swiftdomainhosting.com/favicon.png  404 
12/07/2026 12:26pm  100.54.18.96  https://swiftdomainhosting.com/favicon.png  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;
12/07/2026 - 9:07pm GMT / UTC