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:
10/07/2026 6:01am  184.105.139.70  http://213.155.2.230/geoserver/web/  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KBR5T9UJVOZ47SY-EGCNYKZD24XSK5O0  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KE-9BXD57EIOFX5LPVLBG_Z9VYK1SJLY  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I3ZZ_2WD1MWD0_VJJV7QTXXL-6AW0S5-  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NHLI76WIH2W9DH-PLTWNB1-4-VDWEJ72  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/K6DTFZTAX_R1EEF6XDIUYK-0A-WHMOBR  404 
10/07/2026 5:22am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/DUXGBCODVMHFFXPPS_8WFBYBX7V8OC31  404 
10/07/2026 5:22am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/EXI86A6DKF1DGVR2X06C1XV_4XT0B0YT  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-T62706ISQRC2IWWHJRWVX8USM4OFQOU  404 
10/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/J2H3Z8_360B2YQIVDLUDT-PE5ET_0G7R  404 
10/07/2026 5:06am  65.21.143.218  https://agius.co/ads.txt  404 
10/07/2026 4:59am  83.71.10.102  https://agius.co/webwindow/blog/blogpage.shtml  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/credentials.json  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/secrets.json  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/settings.json  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/config.js  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/config.json  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/.env.backup  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/.env.test  404 
10/07/2026 4:03am  158.94.208.36  https://213.155.2.230/.env.development  404 
10/07/2026 3:24am  34.96.46.79  https://agius.co/ads.txt  404 
10/07/2026 3:05am  47.128.60.171  https://agius.co/robots.txt  403 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VK2OIQX2LL1E16KJAWUP93BHRFCUZUD4  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/OIXEHHZR6TWOG5ZMW5D0RF-Z4JC41W0Y  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ERG0QMI3FWLIMQTP6AOFAJTHF35_GU7N  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WESZEMRWSOEPDC32DGTJ4UFL04BX4XJO  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P560AG4CM4UCQFU4JP0SXIW4JU_MQNXP  404 
10/07/2026 2:20am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/B74K23ZKKUR415OQHLF3V640_Q9P1GMQ  404 
10/07/2026 2:20am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/A9FEE3AU5WRVM2UJ0AI26-S22XZCA8C5  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9M9RVO44JX2DCKXQV1ZM4819Y4I750MS  404 
10/07/2026 2:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2TRM96F1_S4E6RDPE2I931IMD9VBK7YZ  404 
10/07/2026 1:04am  156.59.198.135  https://agius.co/errors/error-image.php?Image=..%2Ffiles%2Fclock_01.png&Message=Notfound%7CI.P.value%3B47.128.48.204%7CHostname%3Bec2-47-128-48-204.ap-southeast-1.compute.amazonaws.com%7CDate%2Ftime%3B15%2F05%2F2026-11%3A53pm%7CStatuscode%3B404&Msg2=URL%3Bhttps%3A%2F%2Fwww.directbeers.com%2Four-products&Title=HTTP404-Pageorfilenotfound  403 
10/07/2026 12:18am  205.210.31.100  http://www.http.agius.co/shell.php  404 
10/07/2026 12:17am  198.235.24.219  http://www.http.agius.co/shell  404 
10/07/2026 12:17am  198.235.24.225  http://www.http.agius.co/webshell  404 
10/07/2026 12:17am  209.99.184.231  https://213.155.2.230/package-lock.json  404 
10/07/2026 12:17am  209.99.184.231  https://213.155.2.230/package.json  404 
10/07/2026 12:16am  172.202.117.213  https://213.155.2.230/owa/auth/x.js  404 
9/07/2026 11:57pm  156.59.198.136  https://agius.co/errors/error-image.php?Image=..%2Ffiles%2Fclock_01.png&Message=Notfound%7CI.P.value%3B47.128.48.214%7CHostname%3Bec2-47-128-48-214.ap-southeast-1.compute.amazonaws.com%7CDate%2Ftime%3B19%2F05%2F2026-9%3A20am%7CStatuscode%3B404&Msg2=URL%3Bhttps%3A%2F%2Fwww.directbeers.com%2Fhome&Title=HTTP404-Pageorfilenotfound  403 
9/07/2026 11:46pm  198.23.242.162  http://213.155.2.230:80/v2  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;
10/07/2026 - 6:11am GMT / UTC