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:
27/07/2026 3:02am  154.216.197.83  https://agius.co/os/files/..%5Cindex.php  404 
27/07/2026 3:00am  150.228.29.91  https://agius.co/webwindow/blog/blogpage.shtml  404 
27/07/2026 3:00am  27.3.138.246  https://agius.co/webwindow/history/Help.htm  404 
27/07/2026 2:59am  189.217.104.135  https://agius.co/webwindow/Welcome.htm  404 
27/07/2026 2:59am  190.139.146.197  https://agius.co/webwindow/history/Welcome.htm  404 
27/07/2026 2:14am  47.128.60.137  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%2047.128.60.137|Host%20name;%20%20ec2-47-128-60-137.ap-southeast-1.compute.amazonaws.com|Date%20/%20time;%20%2027/07/2026%20-%202:14am|Status%20code;%20403&Msg2=URL;%20https://agius.co/  403 
27/07/2026 2:14am  47.128.60.137  https://agius.co/files/elecrytears.gif  403 
27/07/2026 2:14am  47.128.60.137  https://agius.co/  403 
27/07/2026 2:11am  38.143.56.67  https://agius.co/administrator/components/com_jce/jce.xml  404 
27/07/2026 2:11am  38.143.56.67  https://agius.co/plugins/system/jce/css/content.css  404 
27/07/2026 2:11am  38.143.56.67  https://agius.co/plugins/system/jcemediabox/js/jcemediabox.js  404 
27/07/2026 2:11am  38.143.56.67  https://agius.co/plugins/editors/jce/jce.xml  404 
27/07/2026 12:20am  164.68.114.55  http://213.155.2.230/___proxy_subdomain_whm/login/?login_only=1  404 
27/07/2026 12:20am  164.68.114.55  https://213.155.2.230/___proxy_subdomain_whm/login/?login_only=1  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GBBFW12XBP2D3H4PDZ0BF9441YW7-LGL  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LYNEWGFNYX7PC69W50OQRGB1R0RP925G  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MNBHOOOIGCM7FGOK324YEXLVU_8C-Z24  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SY_NSNSSRJ0YFU94HK8UT50529KTA1KK  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BU4SLAIEUO5MXAAWPDQ9YLKCZCT9MS5G  404 
27/07/2026 12:19am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/NKAE_OK9Y603I1FVC_R7VAYAEOD-XLL-  404 
27/07/2026 12:19am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/O_XJ57KCYK-PWOJVRHNX8RT2O39FN_VQ  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BY9CM6YP_E4_VDSIGEQ9IX7JZOIBTK50  404 
27/07/2026 12:19am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LP6BMQ8A__4-LO6Z8HKNTLS6SY4UUV-8  404 
27/07/2026 12:18am  164.68.114.55  http://213.155.2.230/web.config  404 
27/07/2026 12:17am  164.68.114.55  http://213.155.2.230/app/config/parameters.yml  404 
27/07/2026 12:17am  164.68.114.55  http://213.155.2.230/config/database.php  404 
27/07/2026 12:17am  164.68.114.55  http://213.155.2.230/config/config.php  404 
27/07/2026 12:17am  164.68.114.55  http://213.155.2.230/actuator/logfile  404 
27/07/2026 12:16am  164.68.114.55  http://213.155.2.230/config/database.yml  404 
27/07/2026 12:15am  164.68.114.55  http://213.155.2.230/.env.prod  404 
27/07/2026 12:15am  164.68.114.55  http://213.155.2.230/.env.backup  404 
26/07/2026 11:39pm  196.117.10.215  https://agius.co/.env.php  404 
26/07/2026 11:39pm  196.117.10.215  https://agius.co/403.shtml  404 
26/07/2026 10:51pm  157.55.39.59  https://www.agius.co/sitemap.xml  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/new/  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/blog/  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/backup/  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/wordpress/  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/old/  404 
26/07/2026 10:37pm  34.136.118.176  http://swiftdomainhosting.com/wp/  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;
27/07/2026 - 2:06am GMT / UTC