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:
11/07/2026 7:54pm  40.77.167.26  http://http.agius.co/sitemap.xml  404 
11/07/2026 7:08pm  52.167.144.203  https://agius.co/countdown/Image_005.jpg  404 
11/07/2026 6:42pm  180.153.197.166  https://agius.co/ip  404 
11/07/2026 6:42pm  1.92.198.190  https://agius.co/ip  404 
11/07/2026 6:42pm  101.42.54.53  https://agius.co/ip  404 
11/07/2026 6:42pm  112.65.212.242  https://agius.co/ip  404 
11/07/2026 6:29pm  121.91.170.126  https://agius.co/ip  404 
11/07/2026 6:19pm  211.101.237.84  http://213.155.2.230/web-console/ServerInfo.jsp  404 
11/07/2026 6:19pm  211.101.237.84  http://213.155.2.230/invoker/JMXInvokerServlet  404 
11/07/2026 6:19pm  211.101.237.84  http://213.155.2.230/jmx-console/HtmlAdaptor?action=inspectMBean&name=jboss.system:type=ServerInfo  404 
11/07/2026 6:19pm  211.101.237.84  http://213.155.2.230/invoker/EJBInvokerServlet  404 
11/07/2026 5:53pm  47.128.60.171  https://agius.co/robots.txt  403 
11/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/JNNN81IY_U3G8RF23_IDD388TJ8L2JUF  404 
11/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UMV10266OXK82U9HYQS45CLASKK5O3Y-  404 
11/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DGH21WD4N3Q7EY4YBOHB20Q1ZL0HXC2W  404 
11/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/21L76CSZHU30TIOAX9PU96NZXP4HW2XG  404 
11/07/2026 5:23pm  66.249.69.96  https://agius.co/ads.txt  404 
11/07/2026 5:23pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B7IXUQ7QAMS09K5LT2HPPDU3TBX6-RPW  404 
11/07/2026 5:22pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/4PXV6JX_ZNYWA-3VHS1QF0S749J3TCD4  404 
11/07/2026 5:22pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/1TTCZQ6GCTM4NUEVJPOB0IGJF635HJF7  404 
11/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/STJGCAHH-LIA9ZERM-1E02MUWAOJE1U3  404 
11/07/2026 5:22pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DYOM5HAQSRXO4TRT4D-36H0W02B907JX  404 
11/07/2026 5:20pm  197.248.208.219  https://agius.co/webwindow/history/Help.htm  404 
11/07/2026 5:09pm  66.132.224.236  https://213.155.2.230/security.txt  404 
11/07/2026 4:23pm  14.191.83.23  https://agius.co/webwindow/Welcome.htm  404 
11/07/2026 3:38pm  47.128.60.201  https://agius.co/http-error.php  403 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IWDIDU7RL-QRE35CRLB0VNTMSZBGQSF_  404 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/15CVWD19WY7PH3-67J3XAJX0OOR91GPE  404 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1JWX60272A8QCJSK9H099PHRM_8DBI-V  404 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/33VM6_QDQGYYD4LESF-D-NGPY-HGK96S  404 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/0-6EXXI3JM3U4-NNFRU_42Z2DG3EB1HK  404 
11/07/2026 2:20pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/0N0PE5OGWZJUM8EI60LBY7R3DFEHOZWQ  404 
11/07/2026 2:20pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/4B6IBNSKXLYUOHSH46QHT44E85PNHVVN  404 
11/07/2026 2:20pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7614GTO-W7ERKCKKILAIM6WVT1RNM5C9  404 
11/07/2026 11:47am  17.241.227.173  http://www.swiftdomainhosting.com/webwindow/Welcome.htm  404 
11/07/2026 11:23am  43.130.9.111  https://agius.co/http-error.php?redirectcode=402  402 
11/07/2026 11:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/S6XG0PACOW0USH1QH_E_KOSTA_08NAV6  404 
11/07/2026 11:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8N7N3SJW72X567V7DCPPLAZ9QNQSXNEG  404 
11/07/2026 11:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/51_AAUIMP0OH0R0FIOIO-WF5R5_4E6XX  404 
11/07/2026 11:18am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_33A6GGAAF2CRUXU6F6HBBGZRELLU8AR  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;
11/07/2026 - 8:13pm GMT / UTC