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:
23/06/2026 6:54am  196.118.121.136  https://213.155.2.230:443/.env_ci  404 
23/06/2026 6:33am  2.124.182.200  https://agius.co/stpaulstest/pages/images/fonts/NouveauFLFExtra.ttf  404 
23/06/2026 6:24am  170.246.157.151  https://agius.co/webwindow/blog/blogpage.shtml  404 
23/06/2026 5:17am  196.118.121.136  http://213.155.2.230:80/.env_ci  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/82N_YETLQJJAXGIX_5Y2Z3J-IJXVQKV_  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/HAT2KUFLI-28R297GF0OK1_KG9ZEDZOA  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/6IM_UF-NC6RBM7X2OCAG9PY53L98PE_1  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/QA1S2TPXJF8IR4D4T9PGA5NINU2QZT7I  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/2LG3X0P1PSVMG2_JG9P726PPDTJZ2ZUZ  404 
23/06/2026 5:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/5MQ_Q-71385I2JT_E2MPZHP6V8ZLJRA6  404 
23/06/2026 5:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/6RHVL2J9T5UNPBSAD3HP5BSBH6AL-LTX  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3OKINFI6JAS95541S0_QM_TSKSKN64AN  404 
23/06/2026 5:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/AODW_-6DS4SIX5X_4WCTF-6G6HKNVYOS  404 
23/06/2026 2:30am  84.21.190.140  https://agius.co/wp-content/plugins/giftware/public/js/ultimate-woocommerce-gift-card-public.js  404 
23/06/2026 2:30am  84.21.190.140  https://agius.co/wp-content/plugins/giftware/changelog.txt  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3SLWMS_TA9W7OI17QVZHT45OBNWD-MFT  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/3NDUIV-2DBVOUM5Y-UB23JAFKA3410CB  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/X-U3TH-6J2A3QKHI5H2212TKJF8_5-U_  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/OSYCUUBQV1T8ZYL-UAAR3GQRO0M85FH5  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/XPSERZSA-BC_T_WK0X6-FWOEU67J26SK  404 
23/06/2026 2:04am  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/K1-8OW_Y0SZ-71TZCH62_6YOOA3HF8PP  404 
23/06/2026 2:04am  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/5J4JXV5ZQ60PX15NJH905BLVW9-0FIOR  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/P-WPJE7QCDW94VH8U86C3ZIB-OKU2C6S  404 
23/06/2026 2:04am  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/G-P36P886CF7GZ7MT7M4SSIXH_B6IBWL  404 
23/06/2026 1:55am  47.128.60.148  https://agius.co/robots.txt  403 
23/06/2026 1:18am  136.124.34.120  https://agius.co/ads.txt  404 
23/06/2026 12:52am  35.180.68.76  http://213.155.2.230/goform/goform_get_cmd_process?isTest=false&cmd=modem_main_state%2Cpuknumber%2Cpinnumber%2Cpsw_fail_num_str%2Clogin_lock_time%2Cadmin_user%2Cadmin_Password&multi_data=1&_=1722686223667  404 
22/06/2026 11:24pm  185.243.5.120  https://213.155.2.230/polydefault-device.cfg  404 
22/06/2026 11:24pm  185.243.5.120  https://213.155.2.230/preconfig/polydefault-device.cfg  404 
22/06/2026 11:24pm  185.243.5.120  https://213.155.2.230/app/provisioning.cfg  404 
"22/06/20 11:24pm  185.243.5.120  http://213.155.2.230/configs/000000000000.cfg  404 
:24pm" 185.243.5.  https://<  404  Polyco 
/5.4.5.8726" Unknown  Unknown  URL unknown  Unknown 
"22/06/20 11:24pm  185.243.5.120  http://213.155.2.230/sip.cfg  404 
 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/X84JG3W8LMFMOP7FGD9O-IP-QHJ-JP4S  404 
22/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/8ZP71R6KMNWQLDTJ6VITEPK54AYD35I9  404 
22/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/ZK1ERCLMSDA51O6G7OBTDZ80XZUWGY9Q  404 
22/06/2026 11:03pm  213.155.2.229  http://mail.swiftdomainhosting.com/.well-known/acme-challenge/F9NUWDG2I9HYZ15LSAVIHL4BX3142QA5  404 
22/06/2026 11:03pm  213.155.2.229  http://www.swiftdomainhosting.com/.well-known/acme-challenge/U8WIBJ5-RB293SCQUN8MUC80JGTXDCHO  404 
22/06/2026 11:03pm  213.155.2.229  http://swiftdomainhosting.com/.well-known/acme-challenge/7BW_95V7EV3D5C1Z--SPY274WVY-LSTH  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;
23/06/2026 - 7:10am GMT / UTC