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:
16/07/2026 3:21am  69.5.169.117  https://213.155.2.230/mcp  404 
16/07/2026 3:21am  69.5.169.105  https://213.155.2.230/onvif/device_service  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BJG8CVAO1QZ9XP4BJ9S8MMFOLJR3-S0V  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W7EGXWOZ7EK7BXMPT5R7AL0OVMEKQD-_  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ACBD_JEL1CEXOHBBSFNXU6PDL__B8EZL  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/65833K3O7E0V00SBJCVJW29CF29PG-69  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ZTXVAGXLRQXHMG85Q-77E08C2VOAVRHS  404 
16/07/2026 2:20am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/4BU8JJ179ZNS_EZX6-2C7S2O5AK04TN4  404 
16/07/2026 2:20am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/8-STBRVX5I6QK37OVVD96DPUJ_6-_PY1  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LM-2LM3329IJPCW6L97TF3P5UYVWAWYF  404 
16/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_ELCSQ-NDXU41R4O7AV6ZCVV-DR_A4-2  404 
16/07/2026 2:08am  54.225.81.20  https://agius.co/http-error.php  403 
16/07/2026 2:03am  45.234.46.52  https://agius.co/webwindow/Welcome.htm  404 
16/07/2026 2:03am  167.94.146.58  http://213.155.2.230/security.txt  404 
16/07/2026 2:02am  14.234.200.17  https://agius.co/webwindow/history/Welcome.htm  404 
16/07/2026 2:02am  168.205.152.71  https://agius.co/os/files/..%5Cindex.php  404 
16/07/2026 2:01am  168.227.166.13  https://agius.co/webwindow/blog/blogpage.shtml  404 
16/07/2026 2:00am  45.191.99.141  https://agius.co/webwindow/history/Help.htm  404 
16/07/2026 1:08am  114.119.157.245  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
16/07/2026 1:07am  59.96.139.62  http://127.0.0.1:80/GponForm/diag_Form?images/  404 
16/07/2026 1:01am  198.235.24.46  http://www.swiftdomainhosting.com/shell.php  404 
16/07/2026 12:56am  147.135.137.13  http://213.155.2.230/_profiler/phpinfo  404 
16/07/2026 12:56am  205.210.31.227  http://http.agius.co/webshell.php  404 
16/07/2026 12:26am  205.210.31.240  http://www.swiftdomainhosting.com/webshell.php  404 
16/07/2026 12:24am  198.235.24.112  http://www.swiftdomainhosting.com/shell.php  404 
16/07/2026 12:19am  147.185.132.201  http://www.swiftdomainhosting.com/shell  404 
16/07/2026 12:19am  198.235.24.167  http://www.swiftdomainhosting.com/webshell  404 
16/07/2026 12:16am  205.210.31.240  http://http.agius.co/webshell.php  404 
16/07/2026 12:15am  198.235.24.89  http://http.agius.co/shell  404 
16/07/2026 12:14am  198.235.24.249  http://http.agius.co/shell.php  404 
16/07/2026 12:14am  205.210.31.60  http://http.agius.co/webshell  404 
16/07/2026 12:08am  136.124.32.120  https://agius.co/ads.txt  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/27UJN9AVNKBJKHYW-EOQ3F7GNN1VRBYR  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T88UGU7_LFIT8C8PM9MNV_8VG8Y8WE4V  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/X16DFKRT37XXRG9987AVZYFK2FPBYOKZ  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NCU8QROZRAK0RNB0C2QWITT4T_8QCLSK  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QSFFJJEV1BRLD-MF5T9-5MJW7878S2QD  404 
15/07/2026 11:24pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/MFK1TG1-_G6-86ETTVWSBX5RG_PFYFYA  404 
15/07/2026 11:24pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/4AHMV_VSY2IO6-AC4K81KS26KOXWFQZJ  404 
15/07/2026 11:24pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2SAXSKZ-Z19-_A9IYN7JF87IGOIPPX-A  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;
16/07/2026 - 3:30am GMT / UTC