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:
30/06/2026 3:30am  198.235.24.92  https://213.155.2.230:443/api/jolokia/version  404 
30/06/2026 2:26am  34.34.233.6  https://agius.co/ads.txt  404 
30/06/2026 2:22am  34.6.13.114  https://213.155.2.230/wp-json/wp/v2/settings  404 
30/06/2026 2:22am  34.6.13.114  https://213.155.2.230/wp-json/gravitysmtp/v1/tests/mock-data  404 
30/06/2026 2:22am  34.6.13.114  https://213.155.2.230/wp-json/gravitysmtp/v1/config  404 
c OS X 10_5_  like Geck  Unknown  URL unknown  Unknown 
30/06/2026 2:22am  34.6.13.114  https://213.155.2.230/wp-json/gravitysmtp/v1/settings  404 
30/06/2026 2:18am  34.105.148.46  http://213.155.2.230/wp-json/wp/v2/settings  404 
30/06/2026 2:18am  34.105.148.46  http://213.155.2.230/wp-json/gravitysmtp/v1/tests/mock-data  404 
30/06/2026 2:18am  34.105.148.46  http://213.155.2.230/wp-json/gravitysmtp/v1/settings  404 
30/06/2026 2:18am  34.105.148.46  http://213.155.2.230/wp-json/gravitysmtp/v1/tests/mock-data?page=gravitysmtp-settings  404 
 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/F_A0-MG6BJ7MZO7Q-V8-8B9Z9XRSRN6U  404 
30/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/PB1RTR265WC1EZ0GF7KZTZ4ED0QC8CBE  404 
30/06/2026 2:03am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/05J61AVI1466ZX0F_JXXTZ_VP0H-W2YD  404 
30/06/2026 2:03am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/FAH18E0A9X8KUGAK-AXS5JFMAV7T69M_  404 
30/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XKX2CU13G-F9DVECRM55Z_8920KAFQAH  404 
30/06/2026 2:03am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HLZVOSJL7XPPUCCKO4BVIWE1YCXJG-O0  404 
30/06/2026 1:46am  114.119.155.81  https://agius.co/stpauls/pages/videos/PodCast-radio/TheBirthdayCakeGame_S001-E002.m4a  404 
30/06/2026 12:13am  147.185.132.111  https://www.swiftdomainhosting.com/jolokia/write  404 
29/06/2026 11:37pm  103.113.192.157  https://agius.co/webwindow/history/Help.htm  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/SWY23TWZIYRC2VY_QPQGEQ33P1JS-6C3  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/76M6_KEI4L-HI5X65NPC-PE_PYZDZMWU  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/M32IVAP-VX008E21WFPXEYONMBQ8S9J1  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XUK7D-UGM6H_T0MGK42E5B0FTVJO_PB-  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B2NBCR-MPAUMJG1_YYS78X1CZZGE5GXE  404 
29/06/2026 11:06pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/X6B161QXTRUX25UT2R7VEW31-O2H43ZH  404 
29/06/2026 11:06pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/774JL4LDKZDQIF1NH3O7KJE3_RN1H88S  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/VVQ_0VJNWOFBC3NH4XB11JNVM0HV1GZ9  404 
29/06/2026 11:06pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/T-SCNCJC3-ROR6PWZ731QBIYHNJWUWNQ  404 
29/06/2026 10:08pm  198.235.24.137  https://agius.co/jolokia  404 
29/06/2026 9:42pm  205.210.31.55  https://swiftdomainhosting.com/jolokia/list  404 
29/06/2026 8:53pm  207.46.13.154  http://http.agius.co/sitemap_index.xml  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/BV0ACHGXM-EC_IRB8FIDXK_74G4R9-17  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/B3ML7XF1HQTI30X2CLDMTSG7A9U5PY7_  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/DYZ2FTG-2TC8DM5UYVUHP238TD2-T9R4  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/RNK2248NTQQVCJCX4AJZ_7F0ADATTU2I  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/-7BDSIRT6KXYG1S87JGWLWPHRTJ3UN04  404 
29/06/2026 8:05pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/P-Q-YK_9DC0KYLNJEZULJSGQ2FRP88SO  404 
29/06/2026 8:05pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/G-A4L_0U4FVASZFVZGSSKHW_-RJCC8L5  404 
29/06/2026 8:05pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/1GSSF2CA9U1SP-4O7-_0N-NSHJPT0-YW  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;
30/06/2026 - 3:36am GMT / UTC