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:
6/07/2026 12:48pm  3.232.39.98  https://agius.co/webwindow/history/versionhistory.htmWebWindow  403 
6/07/2026 11:40am  144.217.135.244  https://agius.co/humans.txt  404 
6/07/2026 11:40am  144.217.135.244  https://agius.co/llms.txt  404 
6/07/2026 11:40am  144.217.135.244  https://agius.co/.well-known/security.txt  404 
6/07/2026 11:40am  144.217.135.244  https://agius.co/security.txt  404 
6/07/2026 11:40am  144.217.135.244  https://agius.co/ads.txt  404 
6/07/2026 11:29am  216.180.246.63  http://213.155.2.230/admin/index.html  404 
6/07/2026 11:29am  216.180.246.63  http://213.155.2.230/manage/account/login  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HIH02EFZ8Z06AN_ZHTGCDYXL3CHR7138  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/I75G9GMO7OAWU0KJGTC8YO7E-Y7AAOMK  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SV6C43HMURPQYEP7ZLOB6SLUVCAYZ01P  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/5M2RHCAV8HM-W2OPXPQ53WSM8RHCLSGO  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/57MGAHN95VOT0SVOLEOK6IA190ZLMUKP  404 
6/07/2026 11:20am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/QQFCD196ZVNI-XRJOR3N8SQ46DA20-H4  404 
6/07/2026 11:20am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/FK0UKQ_MDR8C-I8IT4DC96PHJJJA3F15  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W-R0NS03Z2J0HUXJC9H0JRN2AUMHSAWD  404 
6/07/2026 11:20am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IUK3A16QV26Q_ZOTCBMW5B1VBXADVJ-Y  404 
6/07/2026 10:07am  47.128.60.133  https://agius.co/robots.txt  403 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E-R5UA-PY4XQ69R8LCTT1S05I9HDNF_Q  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KK8QY7LCQ3Y43RUH0_MBHARGEPFD2N-P  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Y5JYVL2BN0BSGCVN1IKC61_MF-UHTOQ2  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9B3ERD38VYN2VOGW-L46QDW1G1R7Q4NW  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WLHL9A2EZPXMF4E_MCWNGRWB4WELE26K  404 
6/07/2026 8:23am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/IWN_EC3-Y_A140Z2YH_LX4V6BB34XE83  404 
6/07/2026 8:23am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/VTERGJZ4B2UCTZL4_2SHLD15KSMQ73ZT  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QBAHS0L1LHUT709TG55US1QZXYGN670L  404 
6/07/2026 8:23am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6WDC-CL_JRYHH6U_IXTQSHN_CZKIYDUI  404 
6/07/2026 8:14am  114.119.133.42  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
6/07/2026 8:14am  114.119.143.39  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
6/07/2026 8:11am  35.198.224.53  https://agius.co/components/com_sppagebuilder/assets/css/sppagebuilder.css  404 
6/07/2026 7:03am  114.119.133.42  https://www.agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
6/07/2026 5:48am  182.186.102.223  https://agius.co/webwindow/history/Welcome.htm  404 
6/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ZEVZQMJZIYEV002_NST-ZFPMHUPXLOJ9  404 
6/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TJ_B_YGR45QZ1QRONM6QMTX9A82XQON9  404 
6/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XFM0UOB3-L_63CV8ZGI95KRP9L5INI_9  404 
6/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AUM9EM_M6TPLA0OYJBBTD0W8_SKOIGV0  404 
6/07/2026 5:22am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/VDZ1JK00R9N_S50S7-CCO1IL8B5Y30_1  404 
6/07/2026 5:22am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/TS5M-4FK_9DLEJA9BE6_9YJ9RYFP6FJN  404 
6/07/2026 5:22am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/_WLL7MH_T1M3JTSNR9I0RZ-_B6H157TK  404 
6/07/2026 5:18am  51.178.187.227  https://agius.co/404.shtml  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;
6/07/2026 - 1:36pm GMT / UTC