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:
21/07/2026 2:02am  181.79.83.92  https://agius.co/webwindow/blog/blogpage.shtml  404 
21/07/2026 2:02am  113.190.191.72  https://agius.co/webwindow/history/Help.htm  404 
21/07/2026 2:01am  186.14.255.154  https://agius.co/webwindow/Welcome.htm  404 
21/07/2026 2:01am  197.26.178.252  https://agius.co/webwindow/history/Welcome.htm  404 
21/07/2026 2:00am  105.98.175.229  https://agius.co/os/files/..%5Cindex.php  404 
21/07/2026 1:54am  37.157.7.160  https://agius.co/ads.txt  404 
21/07/2026 1:37am  34.96.63.28  https://agius.co/ads.txt  404 
21/07/2026 1:16am  114.119.146.251  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Y92OQPZJIOIB7VA2D3XR_Q7VVFIML3GY  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GC0F1_KCRUME0Q4FXBJENY_EYO3EP967  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8ACGCKWER68SLZD4MF5ME66Y7XVTBAR8  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4Q2QKI416T9IW1AHR46BMA8I9W5ECNNN  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6IBRLTV35W3A7DQ9Y1Q1XN5WYWVH2BQZ  404 
20/07/2026 11:22pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/R8TG8TRUZYPMF8G0QCJ73EWM__59H8GI  404 
20/07/2026 11:22pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/8KK8-MB-_TVH1W6BAIUKCZ9P_3CBV6Q_  404 
20/07/2026 11:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WNCJLY8RTGSUKS6X7EDO43-8CZ4ND41Z  404 
20/07/2026 10:54pm  207.46.13.150  https://agius.co/countdown/Image_004.jpg  404 
20/07/2026 9:59pm  207.46.13.153  https://agius.co/countdown/...t/uploads/2022/04/SLS-Apr-21-2022-8868-800x534.jpg  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2ATJPJKA1G-479_QY1B2JLIBDKLOQX4S  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I6ULASZJ9DW6OL-XU9UKAXKV-Z07UJFS  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NAS_UIJJ8LEWM8GEB65ME90WF2604LLP  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HPBDJXG-DENC05D6YEZTVLGY54PDZ1L_  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/U6IFT5IMZJFUZB69FV9H3QSQCHC198IN  404 
20/07/2026 8:22pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/E9RU9_O5WG2Y-05FRVO4UJ640KVI6I_D  404 
20/07/2026 8:22pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/S6F7CP28VEA374H8PVBKQI0O6NBEE7OC  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AB275MAG-CNDXUP9KE26BB7ORKIBS26Q  404 
20/07/2026 8:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T52-SNU0OVA8P3AG8772W7ZLJCVJBF_V  404 
20/07/2026 5:53pm  66.249.69.97  https://agius.co/ads.txt  404 
20/07/2026 5:53pm  66.249.69.107  https://agius.co/ads.txt  404 
20/07/2026 5:50pm  216.180.246.197  https://213.155.2.230/admin/index.html  404 
20/07/2026 5:50pm  216.180.246.197  https://213.155.2.230/manage/account/login  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XKM2D28GWSG2BH99KFFAF0USF74Y6XBT  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8LI0_I7XS8G0N3Z9LEMRNUIXK9SQ8JHB  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/98LEURLVDOFTA63ADQI1_25M1SX1QC2O  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1Y6HE3G25C_L3KC1GQBAZ7R86YV1EWSV  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PZ63NFSDN720HJAA5OSR4E379JGU_YW8  404 
20/07/2026 5:21pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/BGUW8TJ3DQJHVPX04PO4SI0VRZGR4VC1  404 
20/07/2026 5:21pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/HS5ZP648XO25A4_DMTQA-WBUAFC8HD3R  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1U11QPUZ7QO6YYN-DQAPU9BBDBH1TMQR  404 
20/07/2026 5:21pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LFXMW5I7ZWQGBY7HTTSIPK754M4K4CR7  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;
21/07/2026 - 2:15am GMT / UTC