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:
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/wordpress/  404 
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/new/  404 
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/old/  404 
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/wp/  404 
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/blog/  404 
16/06/2026 8:46pm  136.109.40.126  http://swiftdomainhosting.com/backup/  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/87ZESM0V31C4TQ4KNXT22A4I18YB23QU  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MJLSJVBUT-BFMSXEL7DZ6H5T1XA1JHGN  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Q62JT2NL1418_JYPL7LP73FNP6_VZ04U  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HYT3J0SMMW3G7WYFA-EVDWFJBB6RBV2Q  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LRAZQMANX2--P-PYRY2R94SVZM8H450T  404 
16/06/2026 8:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/26Y7G6PZIEK5GW5WIFPOSE92ICRL7PCK  404 
16/06/2026 8:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/OF_9GRXSU4-TYFKVBH0BZ69ZH63UUCGT  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KHXJEI9IP70QOK3_0Y5_U-EIPBT49-6Q  404 
16/06/2026 8:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-3YTOD19PSB9YOWDCB_T-03INOVDIUA0  404 
16/06/2026 7:38pm  114.119.157.245  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
16/06/2026 7:31pm  45.205.1.198  http://213.155.2.230:80/index.htm  404 
16/06/2026 6:17pm  66.249.69.107  https://agius.co/ads.txt  404 
16/06/2026 5:37pm  5.67.41.100  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
16/06/2026 5:37pm  5.67.41.100  https://agius.co/stpauls/pages/images/fonts/NouveauFLFExtra.ttf  404 
16/06/2026 5:13pm  177.22.44.71  http://127.0.0.1/cgi-bin/ViewLog.asp  404 
16/06/2026 5:13pm  47.128.60.140  https://agius.co/robots.txt  403 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/G1VKY_R3UWCK2XW0MB-T7ONFJ7K16LYU  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CQH80FTVOLLN9X1NOBDJ00OI3VBGJZ8C  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LKN1TI9Z4VIT_MTTD8T0C509T2DZBOQR  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/O-4_P1UJSQYK6_88MY8APFZPTB37PUP6  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_-_O38P2UC2I0YIZ1WF-RG07A1TB72TQ  404 
16/06/2026 5:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/SS2IJY1MQ1IDDBI8BE_53LEFSGOATU3H  404 
16/06/2026 5:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/PQ8HSTJ6ZRFIQ6S2PWT9GRX3APYQR9EP  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FW7LBHWMYUJBSB08WEG1I04DTS5_M_J0  404 
16/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7EP2-_CXY21-3J5JJPU9BSBQJIZOL4Z5  404 
16/06/2026 3:22pm  167.233.65.114  https://agius.co/sitemap.xml  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/51LAO45WZZVK5-I-40XIXFSGVX98ZOW-  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BCBDU1LDJBF5TMS_2ZQIJHRD4_S4GOX8  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/N-2R06SD-1F_KOW6AWGJ-EXDUDPS6F-4  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0Y4TXQVGLANBFL_XXE1N2_4YPUOT2KIJ  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-1BU2DM2C57D06INNOU1MV60PCAQL3E8  404 
16/06/2026 2:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/064RINAEDBJ4-H8Z4W_CXROB520BNTV_  404 
16/06/2026 2:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/W-JPDK_80C7HU-NIAVS4YC59JWN7SM_1  404 
16/06/2026 2:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BA6W2_JVQ1XZMYEPFOXS58L17E-NFEML  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;
16/06/2026 - 8:47pm GMT / UTC