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:
9/06/2026 11:13pm  45.198.224.188  http://213.155.2.230:80/index.htm  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JRU30MHPP541IXWBDWMGWN-WTLQLNYHO  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/H5MSUL9GYZ935N8XYL_-1218QGKFVMTM  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-NR-JOQC8F4P9F7GXSU5KRBGMW1J3IL-  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BTYSZWK8397PVRGRBHRIWQHDX086LOY1  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AAXAZXI8QG7TCDDLQQ46QPWY80LL5MSA  404 
9/06/2026 11:01pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/BGDZ6LM8NZEPUK6L203KJ447AWAHB7S1  404 
9/06/2026 11:01pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/_RJHOQI9S7YJCXE82IKE260GIX6L53CF  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/A70O0RBL575HQ5A8SZ5WTBJGML9ULB2Y  404 
9/06/2026 11:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MNOC01KJ-MNA7VCQOK_0LZWB1EJ-NJGE  404 
9/06/2026 10:59pm  167.94.146.57  http://213.155.2.230/q6eckoyccmbwaz  404 
9/06/2026 10:47pm  93.123.72.183  http://213.155.2.230:80/SDK/webLanguage  404 
9/06/2026 10:29pm  43.143.159.114  https://agius.co/ip  404 
9/06/2026 10:29pm  112.65.211.227  https://agius.co/ip  404 
9/06/2026 10:29pm  116.204.103.7  https://agius.co/ip  404 
9/06/2026 10:29pm  180.153.197.214  https://agius.co/ip  404 
9/06/2026 9:15pm  66.249.69.96  https://agius.co/ads.txt  404 
9/06/2026 9:08pm  40.77.167.33  https://agius.co/sitemap.xml.gz  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CJSIHPHAHSBKS-US1P754S4ZTFVT0P18  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AF8W4DU7-IGDG4TISA48800GQUWIWU1M  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/J1LSUL79A1GEGLTPQFFVNE437F8L0NAB  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/POSG0KD0CHY_R2LA66MV-CII7GOMLYRT  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SSRJ4HD5PW42IDBZAOKOZDTA97FNVP4H  404 
9/06/2026 8:01pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/L3F3ZE5AWQ8JHU1P3XLSX9PY_3CY3II4  404 
9/06/2026 8:01pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/WT9AST19FTG35HM07C3_UTXZC7ZR6BHU  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/OEAS5GDSVK7B991ICA1_COABIM6E-X0T  404 
9/06/2026 8:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XGN_I-NBH35FPVVU241DKZ9Z-CM8MDHL  404 
9/06/2026 7:59pm  52.167.144.18  https://agius.co/sitemap.xml.gz  404 
9/06/2026 6:33pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-IEVSYMSIUF_Q3H-JTG7MQMFI58XU7LI  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7MC6XD-M2RL-P5E2HSI2U39GOKIH5DRR  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IHVJ4XTMAAXM13PFX-IKF4BQPJST7B53  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7BCEKNT0D-_VCIBU8862RF29AV4AXO6D  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UPUE-0E57U99CYW9BTD-HDQY8YW253KZ  404 
9/06/2026 5:01pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/JTH9IJCW2W7K1DAXUXYOEWFFYLPC3UX0  404 
9/06/2026 5:01pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/49XVW9XTTPBS63I4TZ4UFKUJXQ-41IN3  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AHRJ8Z-KVFA-NKBWMVFV9KMZZGKVQLI9  404 
9/06/2026 5:01pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T6LRFQMD5UQX16BI-V2U5D9_3P9LKZPV  404 
9/06/2026 3:54pm  5.67.41.100  https://agius.co/stpauls/pages/images/fonts/NouveauFLFExtra.ttf  404 
9/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_R0O9RN_Y4L5BQECBLVLMXLW0ZVT_04S  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;
9/06/2026 - 11:28pm GMT / UTC