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:
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/wordpress/  404 
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/new/  404 
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/blog/  404 
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/old/  404 
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/wp/  404 
23/06/2026 7:00pm  104.196.170.117  http://swiftdomainhosting.com/backup/  404 
23/06/2026 6:58pm  173.239.213.80  https://agius.co/wp-includes/css/buttons.css  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BXGS7-4-ZZVIVKGCLUVL2LFPG7RHHHK6  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7WNBOWGB_2X-63JGABFMLN54GX40NRW7  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VB87E2SKA5OGPMBWX-_VKMRWNHOLISC2  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/FA26NHO14EA72UXWXLPBAL07A6N8K8IF  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SF5HKLSDXZ0NU0140TLDINK_V933_2RA  404 
23/06/2026 5:04pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/ROINJ6ZWKE1URTFDWXPZFY95RJ86QSYC  404 
23/06/2026 5:04pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/ZC0UM46YD5SWG0S9WRV2AXGQLMHVNWEM  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JUSCS0CVB4T8795-HAVCCSG2VRQN4O20  404 
23/06/2026 5:04pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/V-MKZ8RZF881R77606BHVPDMKZ1ECA5O  404 
23/06/2026 4:48pm  66.249.69.96  https://agius.co/ads.txt  404 
23/06/2026 3:28pm  217.181.91.61  https://agius.co/wp-json/gravitysmtp/v1/tests/mock-data?page=gravitysmtp-settings  404 
23/06/2026 2:24pm  47.128.60.169  https://agius.co/robots.txt  403 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0VBMM48OTMVTAEOM2C_-TB0GCW5D2XRI  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3K13NDC4387MX5B4N4WYIYU8FLMX6HWL  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JIMTL9GWM19-GBPKYNS_6BKLUBNESNEX  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5RFOM0ZQIWZFACL-EW3D-YP9GBTQETFQ  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RIYC4CULWMT9QNSWD_S4RZB1MOZUV5UL  404 
23/06/2026 2:03pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/7QITN-RPFDBM7GCX6HRVYZ-XVTOIXVCJ  404 
23/06/2026 2:03pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/T0_2ML1V3_1MDA2K8GUHUO_5HYO_SOUZ  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6RVTWYU86HWK58MAQQFI2IKHGK2-M-GT  404 
23/06/2026 2:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/G60LZ3G4JX7CJD18K-RU2HWFT9S-W86V  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_O26QX_-SPN-VDGOZ_RNAS_80O34E_PV  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/17XESQZ70OH6NU5UWQLV7EG8KPJVBK56  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/U0XOJ2-CSPCTVK7Z68LHWAAQZTMDSIX3  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RMAFUNPF2IIULY-CDFI4ILIBVNEA5KXD  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-671KLIKZGWQS7BUI6_TH68EQ6UPIQTC  404 
23/06/2026 11:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/Q-CN0XT-TY_HCU6P0_ADNF4RT6NSIHV1  404 
23/06/2026 11:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/DOXY865_RV26ZH_HA95XSB93SDSJNR7G  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JAN5AYC7GVHI0OGC90492HCUTBS2T3IJ  404 
23/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UWJCI_SHJ7XQ_YQW2PN7YH0GLE5E_XA4  404 
23/06/2026 10:24am  181.64.64.124  https://agius.co/webwindow/Welcome.htm  404 
23/06/2026 8:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GKW_RVIZ3NABNTXRIWK7FYD-K71J17MD  404 
23/06/2026 8:05am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/COYB2JT8-VA-0AHG67YDUB9PGIT__LU5  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;
23/06/2026 - 7:10pm GMT / UTC