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 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/OX0SUBAWFJX1CRJE1TJ4BINVK3IFFMG9  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2DXACPOEZX02IO0VVA8YHEYH64S_-BVB  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/F5IO8_IIV84PZPU272KYRFH_I3UA49JQ  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5MO7-GBHI7R4S04P5CPNUE9OLZTJ8PGN  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GHA4-XRRGBX5VYLWKCMLSIMKVUV5SQMX  404 
18/06/2026 11:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/KE0MBV-IPM6992LA-N0BMXWCH5TWL5TX  404 
18/06/2026 11:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/QZ_86F_R2R5IMB_39DZ9835_39-CFDQ8  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/K-D411ES2T4GJYC0XZNOSXK85XTNFL-Y  404 
18/06/2026 11:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NTYAUSY7B0ECIJD26JGYQUM8347R_YY5  404 
18/06/2026 8:09pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/R2_4V4Q-JY07K54MFVSOT6OUKO_387YD  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HM4RO88VJWXS4YYHUE01IAKZ86XRZVRW  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-LRRA7839C7KP9RK_QKNAI3UD89TDHD7  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ZGSQZ1K7OYY_VDOMS0IQVJLW7J2DZ5_Q  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TVATCM90UW53U39C2LD9MHNUEB5LP1AQ  404 
18/06/2026 8:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/BOEFVIX8XHAC-IKT3ZUIW-ZV6108WY5E  404 
18/06/2026 8:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/ICJ1ANVJ20J2JMY_N4_YR0-FT5HC2QBK  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Z7EXW1M-MCA4893U-O7192H15F3VRV42  404 
18/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PEGKMOCLM2-U2O97D69WLCLH7AR5Q29D  404 
18/06/2026 7:44pm  170.106.72.196  https://agius.co/ip  404 
18/06/2026 7:44pm  43.156.93.76  https://agius.co/ip  404 
18/06/2026 7:44pm  43.155.40.24  https://agius.co/ip  404 
18/06/2026 6:58pm  114.119.155.81  https://agius.co/os/survey/index.php?Data_ID=2016-08-12-Test  404 
18/06/2026 6:53pm  163.5.16.8  https://agius.co/stpaulstest/pages/rotaList.php&loadrota=true  404 
18/06/2026 6:40pm  114.119.133.234  https://agius.co/stpauls/pages/videos/PodCast-radio/TheBirthdayCakeGame_S001-E002.m4a  404 
18/06/2026 6:09pm  43.138.126.223  https://agius.co/ip  404 
18/06/2026 6:09pm  180.153.197.90  https://agius.co/ip  404 
18/06/2026 6:09pm  121.37.82.41  https://agius.co/ip  404 
18/06/2026 5:53pm  40.77.167.10  https://agius.co/stpaulstest/pages/rotaList.php&loadrota=true  404 
18/06/2026 5:35pm  5.67.41.100  https://agius.co/stpaulstest/pages/rotaList.php&loadrota=true  404 
18/06/2026 5:19pm  66.249.69.107  https://agius.co/ads.txt  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5O4TLC8SM2VC-QF7_-LC6IWBH72IPI7U  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5UB9M6I-BZGTUZOQ68CX2CFKCDAO6Q8V  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4YVX250NDOFVVPL1W8YJ1_1SVAVCM6AS  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I4H4CGDAL0WQRIXN_-8VH6LQPMA7YAUS  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Q1LUC6VBY4HIEL4U5BH6L3H6JHB6QFK9  404 
18/06/2026 5:05pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/63YV6ZO-I8EAKNZIF4YAU0OHJWXKXH2N  404 
18/06/2026 5:05pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/GSMQ13U29B2GVJPH-AKJOKUOOHEQXC4U  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SY0CQ3-8NG5SMY35RSKY6_82T0JLKNQN  404 
18/06/2026 5:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/C6FZF7NEF4IB2J4CD7AVVYY4KSR-_YP8  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 - 11:57pm GMT / UTC