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:
19/07/2026 9:03am  47.128.60.197  https://agius.co/robots.txt  403 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LONTXNHM2SMPRK8DS-ERWFS51IQ1_9Q_  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DP-F3-ZK0RT4R3TY3SDURCVHQF03JV2Y  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/68Q3J_GZMHO6DGPR3-8AU_NKKLKG7_EP  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DIVGANESURJIZ1JVM0INO9440H4MJC04  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4V2K7LT85MDTL9IR3BJ34RAG8285GJRZ  404 
19/07/2026 8:21am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/Q_OLWTISNCSNH06_YN-EOU9D7DR19TG7  404 
19/07/2026 8:21am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/_6UM_TRBBJ3HAYFJK5YJZNJ4-4QLTVRX  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IZZP1JVK0FAEHRKWZ7JN_2ZTJFTG63IL  404 
19/07/2026 8:21am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/A8V_F81LVAPCC1GZDNB8ZXHFESHV42TH  404 
19/07/2026 7:01am  193.37.33.27  https://agius.co/wp-login.php  404 
19/07/2026 6:29am  198.235.24.82  https://213.155.2.230:443/.well-known/security.txt  404 
19/07/2026 5:46am  40.77.167.144  https://agius.co/countdown/Mars-animated_011.gif  404 
19/07/2026 5:34am  114.119.133.234  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MP__BXQ0YB667_ZO-6ZBD4VFI9QP1CSS  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B2XP85_HRF46ICWC25Z2IXACME6Y3667  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6HVS6CX_2214P1HMYD9IR4CXO5E8EEMQ  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I46JX_2MB1N2ZHTCRR6KIDRFK6VF03S9  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LFLJSLCJF91ZKN5DSPH52ZARLDW0LQ2U  404 
19/07/2026 5:24am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/O3WLJOW0WFOBYSX1B9V_M-30_DAHW1CO  404 
19/07/2026 5:24am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/6EEBUEV-92QESPDMHOQMACZ4LJ8WAELK  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1_Z_Q0WKC60DK3GUS00A_QZQNVX_EW-Q  404 
19/07/2026 5:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1IEBU3B---7G6WY5W1BITEV04MR48301  404 
19/07/2026 4:46am  9.151.203.159  https://agius.co/WindowsLogos/Windows2000.png  404 
19/07/2026 2:43am  5.39.1.246  https://swiftdomainhosting.com/webwindow/history/Welcome.htm  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-DQN0EWJF4705FKUZ_Y3TRZNS_OKXP-6  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E4UN71UXD2AQCQ6H1BEZMO8HIN_CTFY4  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2ORPS-GL4IB28GKNA0PK22B6J56X7YS7  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KRIG943KGAFJHB03LYNTQRRSG04A28UU  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/S6RI32YEVVAHTUATJ7DQI5UE14HB0J2Q  404 
19/07/2026 2:18am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/LBZTL4WVHPIL0UWF4ULSZX897R2SOFT_  404 
19/07/2026 2:18am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/-E3RW9QWUTZL-367T04-JGZ12G_KULJ_  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MLXVHASB54Q2A_G3G2EV24NBWKVF31AP  404 
19/07/2026 2:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/H9_0I5XGJLDKSGGG1X5C-IX0CMCFV22R  404 
19/07/2026 2:04am  190.112.194.84  https://agius.co/webwindow/Welcome.htm  404 
19/07/2026 2:02am  105.163.158.72  https://agius.co/webwindow/history/Help.htm  404 
19/07/2026 2:02am  41.90.35.14  https://agius.co/webwindow/history/Welcome.htm  404 
19/07/2026 2:02am  190.141.140.98  https://agius.co/os/files/..%5Cindex.php  404 
19/07/2026 2:00am  14.231.174.58  https://agius.co/webwindow/blog/blogpage.shtml  404 
19/07/2026 1:07am  65.21.143.218  https://agius.co/ads.txt  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;
19/07/2026 - 9:07am GMT / UTC