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:
21/06/2026 2:24am  204.76.203.219  http://213.155.2.230:80/SDK/webLanguage  404 
21/06/2026 2:11am  14.235.197.5  https://agius.co/os/files/..%5Cindex.php  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/IZ65ZQ51OAPIJRWC5FCEFTJWNEJ1-BON  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/MIA61ZNLH5C-5K1_2_IVB1YSABKIAL6B  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/GUAZAKYB5L4S0I5ZQ_RCH0T9O4LMW2NW  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8_53VSHX_81DSMHCHSFNXRVHRBHPA90P  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2SY_LG2E9JFUNZRXTV02WS7JJX43SXGX  404 
21/06/2026 2:03am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/L5RLQZ1Q1-1NMCT68JJX4ZNF8IX8ZR8_  404 
21/06/2026 2:03am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/FM_MSAPAL-WQ5N3RZF646VH3KGK_UBRU  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/UVXAOSRW--A_SQ7EB6NMHEVQ5V3W20UG  404 
21/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/N1FBQZPI_BZ1MR8S5Y9KZGJGNREMT0MQ  404 
21/06/2026 1:50am  45.198.224.188  http://213.155.2.230:80/index.htm  404 
21/06/2026 1:43am  147.182.244.202  https://agius.co/wp-login.php  404 
21/06/2026 1:33am  146.190.248.112  https://agius.co/wp-login.php  404 
21/06/2026 1:21am  204.76.203.206  http://213.155.2.230:80/SDK/webLanguage  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/C3OKOD3GP3X5LC306-J1X9AL1IM8PDS1  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SQX_V-W8EFR1Q8Z8N_W5-1ZFYOC79WSB  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/TX9A13X5P7G8XPYC5VLUZPN7VD1CWGUT  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/G99PI1Q4N139IUYOFIA0GJ5JPHVDYREN  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W3IFA59P98R_X0VNGMJ637BS58M11RF5  404 
20/06/2026 11:03pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/MO46DYS_ONSNVSFL-0MLF-IE1ZMYN8ZJ  404 
20/06/2026 11:03pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/FWLPX40YO0WXQ5_V8YNHCHBF7MM9E3ZW  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/LTYYN1PIB27PVL3DWV3KQ4EPZLG5S953  404 
20/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/EQNTEPKKX81K8NROZHMXBP2RSEJ-4RDH  404 
20/06/2026 10:25pm  5.67.41.100  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/old/  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/backup/  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/wp/  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/blog/  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/new/  404 
20/06/2026 8:50pm  34.148.96.242  http://swiftdomainhosting.com/wordpress/  404 
20/06/2026 8:45pm  52.167.144.18  https://agius.co/sitemap.xml  404 
20/06/2026 8:23pm  111.225.149.37  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%20111.225.149.37|Host%20name;%20%20bytespider-111-225-149-37.crawl.bytedance.com|Date%20/%20time;%20%2020/06/2026%20-%208:23pm|Status%20code;%20403&Msg2=URL;%20https://agius.co/errors/error-image.php?Image=..%2Ffiles%2Fclock_01.png&Message=Notfound%7CI.P.value%3B47.128.48.222%7CHostname%3Bec2-47-128-48-222.ap-southeast-1.compute.amazonaws.com%7CDate%2Ftime%3B14%2F05%2F2026-9%3A22pm%7CStatuscode%3B404&Msg2=URL%3Bhttps%3A%2F%2Fwww.directbeers.com%2Fnew-products%2Fmixed-case-of-12-x-500ml-bottled-beers&Title=HTTP404-Pageorfilenotfound  403 
20/06/2026 8:23pm  111.225.149.37  https://agius.co/errors/error-image.php?Image=..%2Ffiles%2Fclock_01.png&Message=Notfound%7CI.P.value%3B47.128.48.222%7CHostname%3Bec2-47-128-48-222.ap-southeast-1.compute.amazonaws.com%7CDate%2Ftime%3B14%2F05%2F2026-9%3A22pm%7CStatuscode%3B404&Msg2=URL%3Bhttps%3A%2F%2Fwww.directbeers.com%2Fnew-products%2Fmixed-case-of-12-x-500ml-bottled-beers&Title=HTTP404-Pageorfilenotfound  403 
20/06/2026 8:19pm  111.225.148.171  https://agius.co/http-error.php  403 
20/06/2026 8:08pm  110.249.202.162  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.162|Host%20name;%20%20bytespider-110-249-202-162.crawl.bytedance.com|Date%20/%20time;%20%2020/06/2026%20-%208:08pm|Status%20code;%20403&Msg2=URL;%20https://agius.co/  403 
20/06/2026 8:08pm  110.249.202.162  https://agius.co/  403 
20/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/506W221PM_4MABCAWQ4H5A7SSN-2YNVW  404 
20/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/E4MD6RODV7Z5PZK-S6CBG-IQFGA97I1V  404 
20/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WM5RHK3AUY_YUW8FUN6ZTCMGMR_0FI0S  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;
21/06/2026 - 2:53am GMT / UTC