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:
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-W9FCPGYJC8UIJ570P4XSMI16CQUIXUP  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SND_ESJKD6Y-NDHD6LKXAUT03V285AY2  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6PSVYXXB7U8OPNPZG4GKZ-W9GWLDFADN  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VYG6H6ILUDN4JQ_V7KIF3-54QZC2_O2T  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CWDEH3ZD-MSN--XHXFAZRWOKHQGSCJ4D  404 
25/06/2026 8:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/YTC27AGLJYLBFNWGU-8XWCAQPZ0_EV4C  404 
25/06/2026 8:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/WQHZI9LOIPWGB15NGX35DWFDKKTN2-EZ  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GH6N77MZSU05SHR-IM3OM4RFVMYPY9BA  404 
25/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P8B5HF2Y9P472HZ8YQX5UA8K7UUL4TGS  404 
25/06/2026 6:40am  2.124.182.200  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
25/06/2026 6:33am  114.119.135.139  https://www.agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
25/06/2026 6:29am  71.6.165.200  http://213.155.2.230/.well-known/security.txt  404 
25/06/2026 6:29am  71.6.165.200  http://213.155.2.230/sitemap.xml  404 
25/06/2026 6:17am  64.62.156.162  http://213.155.2.230/geoserver/web/  404 
25/06/2026 6:14am  52.167.144.179  https://agius.co/%22%22.$dir_list[$localloop].%22/%22  404 
25/06/2026 5:14am  145.239.10.137  http://swiftdomainhosting.com/gettest.php  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VV3IXVJ0VCGQ6IA1609A_4V01IIUVESE  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AYDGN_4E4KX__OPLUSJ08IA8U69CCCOQ  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I-WYBDY0ZURZJUK3E9ARDV3-PN0H_7BD  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ZKXM78HVZVC9USU69UI4_9MW4SWI7X58  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/D6BY4LZBBUU-DNCZZUT5S0SQI635G11E  404 
25/06/2026 5:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/YPNYUFY2I75-7JSSK68M_B2LSVSFCNEJ  404 
25/06/2026 5:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/0YAWZJE2E81BAEORUC1OBYTFNPJUD6AI  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TWHTUJFRVOOJWLT6JQBD7CIS0UNXZ86H  404 
25/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FT556EPOFVK4NQFIBP5R9KACJPC6H7_O  404 
25/06/2026 4:40am  45.198.224.188  http://213.155.2.230:80/index.htm  404 
25/06/2026 4:05am  47.128.60.143  https://agius.co/robots.txt  403 
25/06/2026 2:38am  34.96.46.239  https://agius.co/ads.txt  404 
25/06/2026 2:30am  34.224.132.215  https://agius.co/http-error.php  403 
25/06/2026 2:30am  173.215.151.254  https://agius.co/webwindow/history/Welcome.htm  404 
25/06/2026 2:14am  114.119.144.55  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3Y3XCG4M8JWXMRI7Q4BDA56U9_-OI_R3  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MLHT44WECX6I9EAIBJGC16082WA7S_I-  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6EEMI84YFHGZY8IJ4PV5BIRM9O3G60QM  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3TCJFBF1L26PYINN4LZCM4G8SDIH_GYV  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TQYGXA_F9MGUD691PRYB_JYC6H1U4B2-  404 
25/06/2026 2:02am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/ZPDBNPZDMDNR59O6AGC306MU2H68NSDT  404 
25/06/2026 2:02am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/F41EU8NNJ0BP-ECW2E6YT_Y3-WE6SR80  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XHY30GUBMIC9BVK48ECF_P8YJB40_U7-  404 
25/06/2026 2:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XE6LR-SNVYNKM6REGSK73YCEOAF2RHHN  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;
25/06/2026 - 8:29am GMT / UTC