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:
13/06/2026 3:10pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
13/06/2026 3:05pm  222.212.83.51  http://127.0.0.1/cgi-bin/ViewLog.asp  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/V1P7PHO2P2F7P2OACG4FX4_FHZOMDGH5  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4HPO4WYNAR44V__WSR9CODCN7YPSL1OH  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XEAB1XC92247RBACE8SJ-MWG8QQ6V7M-  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/11NC_GLU65GSK4TKKF-5YFOBCKRR4-JS  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-6I34BQZXB2WVMZSK8T_5-3MRK1WSVF8  404 
13/06/2026 2:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/5Q7BH857774PBDU0QPN66UI9G9JWSW14  404 
13/06/2026 2:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/551EAGAY04GTVU4VNCY6GO6BSLHDIAP4  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/EVD37_2X8N982_G3K64PQGDSAHG1B5DI  404 
13/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/74333-NJ2X819N-TYTT3ZLA5EDLAQ478  404 
13/06/2026 1:34pm  5.61.209.92  http://213.155.2.230:80/SDK/webLanguage  404 
13/06/2026 12:58pm  216.73.216.41  https://www.agius.co/webwindow/testpages/Javascript:startOfVideo('VideoPlayer002')  404 
13/06/2026 12:46pm  94.205.179.231  https://agius.co/webwindow/history/Welcome.htm  404 
13/06/2026 12:45pm  64.62.156.38  https://213.155.2.230/geoserver/web/  404 
13/06/2026 12:19pm  43.159.143.187  http://swiftdomainhosting.com/.well-known/acme-challenge/QD9561_IGCQRCPHVA-VR1LXI5A7SRAJA  404 
13/06/2026 12:17pm  129.226.210.142  http://213.155.2.230:80/vendor/vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php  404 
13/06/2026 12:09pm  49.51.196.42  http://213.155.2.230:80/vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php  404 
13/06/2026 12:08pm  43.130.34.74  http://swiftdomainhosting.com/.well-known/acme-challenge/_D-8UC0ME-1DVE8S_D360939-TXJBQZX  404 
13/06/2026 12:07pm  43.159.135.203  https://agius.co/ai.txt  404 
13/06/2026 12:05pm  151.242.30.224  https://213.155.2.230:443/api/auth/validate-sso  404 
13/06/2026 11:58am  43.153.27.244  https://213.155.2.230/owa/auth/logon.aspx  404 
13/06/2026 11:57am  43.157.50.58  https://agius.co/stpaulstest/splashmessage/splashMessageFiles/error_log  403 
13/06/2026 11:49am  43.130.14.245  https://agius.co/stpauls/pages/videos/PodCast-radio/TheBirthdayCakeGame_S001-E002.m4a  404 
13/06/2026 11:39am  145.239.10.137  http://swiftdomainhosting.com/wp-de.php  404 
13/06/2026 11:39am  49.51.39.209  http://213.155.2.230:80/vendor/phpunit/Util/PHP/eval-stdin.php  404 
13/06/2026 11:37am  43.157.170.13  https://agius.co/llms.txt  404 
13/06/2026 11:30am  129.226.95.137  https://agius.co/humans.txt  404 
13/06/2026 11:29am  43.130.39.254  http://213.155.2.230:80/vendor/phpunit/phpunit/LICENSE/eval-stdin.php  404 
13/06/2026 11:29am  43.130.3.122  http://swiftdomainhosting.com/.well-known/acme-challenge/MJQ0OUZNQ3WF33YAXAO7_LG-LMWXQI2X  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NG1UAEBIZYA_8EIQQCPS8O8GGZHSRMFJ  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MJQ0OUZNQ3WF33YAXAO7_LG-LMWXQI2X  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GTL4F191CO9LB6PIS-OOM56JJAM0NORK  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QD9561_IGCQRCPHVA-VR1LXI5A7SRAJA  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B8SE1Z8WXNLKUML3WZMH1A1QEFFT6VL6  404 
13/06/2026 11:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/2A_2C5P4_8WQXZ8KF192L4WG-1Z7LG8Q  404 
13/06/2026 11:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/UVU9KUNKFHTOCOW1J66SUZJT3PJ42YSB  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8-CFNRO-4SE3LQGSA3QMHBZKNZOXGT4L  404 
13/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_D-8UC0ME-1DVE8S_D360939-TXJBQZX  404 
13/06/2026 10:54am  5.67.41.100  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  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;
13/06/2026 - 3:44pm GMT / UTC