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:
17/07/2026 3:14am  45.131.194.213  https://agius.co/403.shtml  404 
17/07/2026 3:00am  34.96.46.145  https://agius.co/ads.txt  404 
17/07/2026 2:50am  86.38.216.231  https://agius.co/file-manager  404 
17/07/2026 2:50am  86.38.216.231  https://agius.co/filemanager  404 
17/07/2026 2:49am  86.38.216.231  https://agius.co/laravel-filemanager  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/old/  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/wordpress/  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/blog/  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/new/  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/wp/  404 
17/07/2026 2:45am  35.229.25.29  http://swiftdomainhosting.com/backup/  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9HRGTTDGY0WKC5ZE0BFK2XA3VPMR3P__  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KK4RFL29P8QTC7030JUEENHT_BT_8BE_  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/700VWR7A4JJH3U2EWJ8F28Q_2_EP8F8J  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/09VO82A1UMLN1KO5104O_H917F0DFWV4  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9155LFYUYS5CJEFWWPD41JWNPZ2OI6US  404 
17/07/2026 2:24am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/IAQ8F9ITKDTNWKEZMOJNP85OE-AD6I-C  404 
17/07/2026 2:24am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/7MW0BZ2KRIWV3F0AW46UPY12BNIYP-K3  404 
17/07/2026 2:24am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/10KJQ7J5EB5FZA8J8GPS3-UA_FPVAKTR  404 
17/07/2026 2:03am  14.231.58.37  https://agius.co/webwindow/Welcome.htm  404 
17/07/2026 2:02am  123.22.112.66  https://agius.co/os/files/..%5Cindex.php  404 
17/07/2026 2:02am  45.7.214.17  https://agius.co/webwindow/history/Welcome.htm  404 
17/07/2026 2:01am  113.163.228.79  https://agius.co/webwindow/history/Help.htm  404 
17/07/2026 1:59am  181.235.138.116  https://agius.co/webwindow/blog/blogpage.shtml  404 
17/07/2026 12:08am  184.105.247.196  http://213.155.2.230/geoserver/web/  404 
16/07/2026 11:41pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
16/07/2026 11:33pm  52.167.144.181  https://agius.co/countdown/Image_005.jpg  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TNK7-ZFJFV7M_KBYIX07G_Y2SMZ-N88G  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IFUVT_BEKE1WWYEIKU11_UZGU44OCJS-  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7X5CG4M8ELY3GF-E5KJ4883KSDRIH8PG  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/J2F68TLLOT41L9GJPZ1EY9MUSRH2RY57  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-9N6RRZ9H9TFJ8T8T8D-LW9OZ8BWYTPQ  404 
16/07/2026 11:23pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/FZ2U3UFPC0B3F3JY7MET33IALQP4TL1F  404 
16/07/2026 11:23pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/JEPYIDLEUY58B_5821HBBMFTZHPA5FK0  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/U5-A7LGPLWD2XSAW6SDRNCO91G5N3_O3  404 
16/07/2026 11:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VSOBZ59MXFE1SMTRFRGQ_LSREEERDGMY  404 
16/07/2026 10:46pm  165.227.191.159  https://rhea-230.uk2group.com/dist/..;/dist/  404 
16/07/2026 10:46pm  165.227.191.159  https://rhea-230.uk2group.com/dist/%2e/  404 
"16/07/ 10:46pm  165.227.191.159  https://rhea-230.uk2group.com/dist/;/  404 
 Unknown  Unknown  URL unknown  Unknown 
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;
17/07/2026 - 3:47am GMT / UTC