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:
19/06/2026 11:48am  45.198.224.188  http://213.155.2.230:80/index.htm  404 
19/06/2026 11:04am  204.76.203.206  http://213.155.2.230:80/SDK/webLanguage  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DR-MRSO0WY-9MQRI4QM6IPPRL9Q_VG9P  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WUB97Q8CA5NU-BWLJWC_V-J_PO85K7D6  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1KPQLOKBBVN35V027TEFFVR6-GGB9JCV  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/9YG0Q3RK_OLP7O98FHN_EXC1UXLPPSDC  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-2Y2W-XXKLZ612MV0DQAIGSBTVS1_9DO  404 
19/06/2026 11:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/EGRI93ZLC7XJ5MNW16GQPXECLA0XZLHH  404 
19/06/2026 11:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/Z0J0ZIJLWJ_6K9K4JD1E2NUBJZ_3WE7I  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Z8DYY-7N37TL_PNE1U7QMZSIO001L2E8  404 
19/06/2026 11:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/4HVN9Z7__AUU1WUPAZ0971NGVFKONNYL  404 
19/06/2026 10:57am  185.12.59.118  https://213.155.2.230/Dr0v  404 
19/06/2026 10:38am  47.128.60.154  https://agius.co/http-error.php  403 
19/06/2026 10:34am  47.128.60.160  https://agius.co/http-error.php  403 
19/06/2026 9:44am  204.76.203.219  http://213.155.2.230:80/SDK/webLanguage  404 
19/06/2026 9:39am  114.119.143.39  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
19/06/2026 9:37am  66.249.82.160  https://agius.co/.well-known/traffic-advice  404 
19/06/2026 9:16am  114.119.135.139  https://agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
19/06/2026 9:16am  20.65.193.105  http://213.155.2.230/hudson  404 
19/06/2026 8:34am  5.61.209.92  http://213.155.2.230:80/SDK/webLanguage  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/W-L9L6PFOB2T-IKJIFWTWSCM2WAALBJN  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/NFIKJU_83Q1FDG5WIQQO5T7NUX07ZO59  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/L-X0WQ8U--JA63YL-S_A8EJ8U1T14VIQ  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ROIBIU09_AVMLX_6FX2YDS1LMN4ZHTS6  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PCYCBYG799Y721O7SOR715N0NK30F4G9  404 
19/06/2026 8:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/5-FSIDUR7I-9V5KRO3_9FVSV1I811JC6  404 
19/06/2026 8:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/QA54UKW4PE7IHLSGE64P1BP0G-_1QRYP  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/Y8PR_SBLSJG7NZA1AIGGSQB5L8AWWWL_  404 
19/06/2026 8:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/860IRCER4N-BIU_A7KMD5_PUH-42TZM-  404 
19/06/2026 7:02am  114.119.157.245  https://www.agius.co/webwindow/testpages/webpages/scripts/romanscript.js  404 
19/06/2026 5:19am  20.29.24.90  http://213.155.2.230/developmentserver/metadatauploader  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/YBK97YKO7YD0T5B_ALOC87N5YS040JCZ  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/74-SEMSNDCEUPCWDFGA66OXZBBT9XWOE  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/WCZK61PUCQ14KT4R70-VWBI6-VF8-0WF  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/KP--LDQ8UD_MCYNIYLOOW4IDI2F0GGWS  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/33LWEV9LT64HIADG8-LDTRDINP5H8MMU  404 
19/06/2026 5:02am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/LZ_CZQM6F1GI7F5H09NQHXJXWCUN_2L-  404 
19/06/2026 5:02am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/XNCY-7I1AE1I3HP50Q10PW3NH2DVHOQO  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/21D70ZZXGRSGIXZXJ6-ZU2QKR_RWMIII  404 
19/06/2026 5:02am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VBRDX8U0VX0K23PETKZBDYQXK24RDR65  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;
19/06/2026 - 12:01pm GMT / UTC