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:
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VHUTEH9O_WBSXP94IWIGNIGSFMB_ZT5M  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AA7LI61ZW2Q9FAPDEDEEPM1QYFB8UF9V  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AFXJ-U3QK9Y79NE75CF0TLGM1FYNGOFZ  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/G_KDR7A_FK3PV0_Z-E8-Q27B4QC81W3U  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/76OND36FAQF5MOPI8F-GSPZ112JH89G0  404 
18/07/2026 8:23pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/L94EPUE5LS8TJUJWPXNBUJSC66_9G3EZ  404 
18/07/2026 8:23pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/4ILPS7_X8ZLX6Q9R1QOHPLTZ867Q43KM  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0DF0KZ53QCEIP-0YHRGT436PZ554VRYE  404 
18/07/2026 8:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P3YQ0PYOD72L6WRMP4T_UERB37Q-R2RX  404 
18/07/2026 7:46pm  2.124.182.200  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
18/07/2026 7:38pm  188.119.8.58  https://agius.co/readme.html  404 
18/07/2026 7:38pm  188.119.8.58  https://agius.co/wp-login.php  404 
18/07/2026 7:38pm  188.119.8.58  https://agius.co/wp-json/  404 
18/07/2026 7:38pm  188.119.8.58  https://agius.co/wp-json  404 
18/07/2026 7:38pm  188.119.8.58  https://agius.co/feed/  404 
18/07/2026 7:05pm  195.182.16.23  http://213.155.2.230:80/SDK/webLanguage  404 
18/07/2026 6:06pm  207.154.253.234  http://rhea-230.uk2group.com/admin/dashboard/stats  404 
18/07/2026 5:53pm  66.249.69.96  https://agius.co/ads.txt  404 
18/07/2026 5:24pm  206.189.36.62  http://rhea-230.uk2group.com/admin/dashboard/stats  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/04BLACI3EEI9FOLIMWS-GDGRFUU_UVYQ  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/D3O_CB-3WH5N0XSYNLDI2PH4D5US-YCH  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RD9GQ87QOXDAWXYAL4ZSXNWGB4EH3CSA  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8M8HOZKDW7JZ58MY-278CBV5HMBL-Y_3  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WC5560Y608YOMAUACZPJV1G8MVIU_VTM  404 
18/07/2026 5:23pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/7-JNT_CHU8GUUBX0PJHV-VEDOI0Q1EXU  404 
18/07/2026 5:23pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/FKHP1W-ZMG4KJ4O4V7S-7E0PQM06_4DI  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2I7K8ND1T8KJDROHM3WG6K9AY706M49R  404 
18/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FRUEMCODUHODJ46QMDY898CH_D144E2G  404 
18/07/2026 4:57pm  168.144.118.196  https://rhea-230.uk2group.com/admin/dashboard/stats  404 
18/07/2026 3:24pm  47.128.60.125  https://agius.co/http-error.php  403 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ADBYJTVH2KZNFL2EYVLH2SHJ9K56ZN4Z  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NSAGHIDXC09-B4_4HXSUC3QPNLX6CBV5  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0862MF-XN7DN5II-FRF5VHSJ4MUWS66C  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CU8HV5SQS8_G0N4FV38GCBXA210WMQHX  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/J53P2Q3PGMFW0F09GW4GL1RPXQB4K3HT  404 
18/07/2026 2:24pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/M-28CWH0HB9NS1N5I7AMKV9VI21_FTK7  404 
18/07/2026 2:24pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/GHIGETCKAQNZBLQW7PJYZ12_18XUF9ML  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XGQJ6Z1SNWD6KADOY-W1YTIP05HMWGZV  404 
18/07/2026 2:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/X5CNRU4DLETL1JVZLCLJAODUCORBD4Y_  404 
18/07/2026 12:18pm  47.128.60.182  https://agius.co/robots.txt  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;
18/07/2026 - 8:30pm GMT / UTC