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:
14/06/2026 7:44am  68.183.172.166  https://agius.co/wp-login.php  404 
14/06/2026 7:19am  147.185.132.141  http://213.155.2.230:80/.well-known/security.txt  404 
14/06/2026 6:27am  48.217.87.78  https://213.155.2.230/owa/auth/x.js  404 
14/06/2026 6:24am  198.235.24.19  https://www.agius.co/.well-known/security.txt  404 
14/06/2026 5:09am  114.119.155.81  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
14/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/F7DTNOLW9TJO9IAYW63JJ_NX05YW_B9G  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_3EICP4B_PPLRSUMJRQLAJU42SJA6F2T  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IL5N51GJ6ZI66E3V9WB1U3Z4MHLAZW95  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VZ2SQ1AIG6CBLZ5POEQC5OZ2H3UAB8F5  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2RARTP5913UL0_AAHNTHT8KSKLSWORTE  404 
14/06/2026 5:03am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/HJ2CQ5G3_HU10CE55YW9XMUQ909MT27S  404 
14/06/2026 5:03am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/HIY050AK3Y886C3YZN03ZP2Z4772PTQS  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NN89G8ULGWU-B5KAA2Z5GEO0PJ7DM4FH  404 
14/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TSNPN2NNLEG0WINBYFU6IFY4YUDAZ__V  404 
14/06/2026 4:39am  220.202.112.238  http://213.155.2.230:80/version  404 
14/06/2026 4:39am  116.172.200.122  http://213.155.2.230:80/v1  404 
14/06/2026 4:14am  188.113.211.169  https://agius.co/webwindow/Welcome.htm  404 
14/06/2026 4:14am  45.142.154.45  http://213.155.2.230:80/v1  404 
14/06/2026 4:14am  45.142.154.45  http://213.155.2.230:80/version  404 
14/06/2026 3:34am  45.205.1.198  http://213.155.2.230:80/index.htm  404 
14/06/2026 3:19am  213.180.203.136  https://agius.co/age/files/websitelogo.ico  404 
14/06/2026 3:17am  66.249.69.97  https://agius.co/age/files/websitelogo.ico  404 
14/06/2026 2:15am  66.132.195.42  https://213.155.2.230/security.txt  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CW1KNR51B_-M63RJ7RB1S_5HGO5VX5AV  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FILWYUBBQ3DA8H3_QEC6J7W8BSPFPTDY  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9HEIS2I28OL-MZ-B9SLOHON65DNODCQO  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PW-UG4D01XHCWAV1XF1PLNVDP39DH4ZV  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0QAZ1PTWMJ9C_V4X6D4P-2F1N319-8-O  404 
14/06/2026 2:05am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/EAR66W2JCUSU_FLXS4OL89MB907VW4RW  404 
14/06/2026 2:05am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/YG2RZB1VBTO2UI73WR4-QQUBDTLDNMQX  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DHMAO8F5ORCS3EC7IARJPFZ3D_-ZP59-  404 
14/06/2026 2:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2HP2SIFW3HGAS9PFSWVZYNAPY5MBV1J5  404 
14/06/2026 1:38am  40.77.167.24  http://http.agius.co/webwindow/Welcome.htm  404 
14/06/2026 1:30am  176.65.139.140  http://213.155.2.230:80/boaform/admin/formLogin  404 
14/06/2026 1:25am  31.14.254.14  http://213.155.2.230/mcp  404 
14/06/2026 12:30am  65.49.20.68  https://213.155.2.230/geoserver/web/  404 
14/06/2026 12:27am  198.235.24.109  https://agius.co/webshell.php  404 
14/06/2026 12:10am  205.210.31.52  https://agius.co/shell  404 
14/06/2026 12:10am  205.210.31.73  https://agius.co/webshell  404 
13/06/2026 11:20pm  5.61.209.92  http://213.155.2.230:80/SDK/webLanguage  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;
14/06/2026 - 8:01am GMT / UTC