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/06/2026 10:36am  45.198.224.188  http://213.155.2.230:80/index.htm  404 
18/06/2026 9:34am  114.119.146.251  https://www.agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
18/06/2026 9:34am  3.87.27.156  https:///server.js  404 
18/06/2026 8:55am  204.76.203.219  http://213.155.2.230:80/SDK/webLanguage  404 
18/06/2026 8:07am  31.14.254.45  http://213.155.2.230/sse  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XAGNEH_8O2AYDKT5UIFOY30C_YZ17VS8  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-Z44DUQT73KR831YQK269S-Q--V1U4B_  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P-3K37WAAAYOFCD8LEHRY39RDC1KYW9V  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3HJH3548Q8AXFCPKP0RPDDK7YI1YIMY8  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PFVPOE7XXI_171G4BNA1T2MBU-L72ALH  404 
18/06/2026 8:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/DEO8TQQ3-Z1P8KMWT0E7KGRB2C4AGABR  404 
18/06/2026 8:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/VN1T3BYUFDCO2Y7JZLN4ZL3VTREA8AWH  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LETZ6VCM_O1FWCTBGTLUS5V5_RCGIIB0  404 
18/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_Y6CUOGWWCH70F_MIX61FZB32G6L7F8J  404 
18/06/2026 7:11am  20.168.0.218  https://213.155.2.230/ecp/Current/exporttool/microsoft.exchange.ediscovery.exporttool.application  404 
18/06/2026 6:38am  37.230.196.62  https://www.swiftdomainhosting.com/sitemap_index.xml  404 
18/06/2026 6:38am  37.230.196.62  http://www.swiftdomainhosting.com/sitemap_index.xml  404 
18/06/2026 6:38am  37.230.196.62  http://swiftdomainhosting.com/sitemap.xml  404 
18/06/2026 6:09am  219.138.41.132  http://213.155.2.230/evox/about  404 
18/06/2026 6:09am  219.138.41.132  https://213.155.2.230/evox/about  404 
18/06/2026 6:09am  219.138.41.132  http://213.155.2.230/sdk  404 
18/06/2026 6:09am  219.138.41.132  http://213.155.2.230/HNAP1  404 
18/06/2026 6:09am  219.138.41.132  http://213.155.2.230/nmaplowercheck1781762974  404 
18/06/2026 6:09am  219.138.41.132  https://213.155.2.230/HNAP1  404 
18/06/2026 6:09am  219.138.41.132  https://213.155.2.230/nmaplowercheck1781762974  404 
18/06/2026 6:09am  219.138.41.132  https://213.155.2.230/sdk  404 
18/06/2026 6:09am  5.61.209.92  http://213.155.2.230:80/SDK/webLanguage  404 
18/06/2026 6:01am  51.15.120.218  http://127.0.0.1/cgi-bin/ViewLog.asp  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3-MRYLV2LPYQ0-2K85MSCHHUBN_BF4J0  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WFCA2WSPCAB1KHMZJ20C_O4F2Y9AMMWX  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LT4Q9_HD8B7-02O8VGGXYPK3SUSUSS48  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/U91-DZLE042K3WF8RFS072PW2IAX-KL6  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B6X_96O-CF7_L5NLU0ZKZNXLDY2ZXJEQ  404 
18/06/2026 5:03am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/Y984JTYH6I9K349_X46BPP-D_MB25OW_  404 
18/06/2026 5:03am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/RNG1-J2AQ6W30O75LRNGESGDJT_EQH10  404 
18/06/2026 5:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/F1UZK73NZ546_4KYGZI_-16596W2FWDF  404 
 4:39am  51.15.80.26  http://127.0.0.1/cgi-bin/ViewLog.asp  404 
18/06/2026 4:26am  84.247.178.219  https://agius.co/plesk-stat/  404 
18/06/2026 2:08am  128.201.100.198  https://agius.co/webwindow/Welcome.htm  404 
18/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Y8PHLRG_PAYIPR-NGD2IG_SIPKHKKXV7  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;
18/06/2026 - 10:50am GMT / UTC