mailural.com is UP 100%, 0.491 sec, avg.
Result for effective on Feb 15, 2026 06:57:17 (UTC). Retest now or Do a new test
| Checkpoint | Time, sec. | Status | Server IP | Location | Code | Content |
|---|---|---|---|---|---|---|
| Asia Pacific (Sydney) | 0.738 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| Asia Pacific (Hong Kong) | 0.554 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| Brazil (São Paulo) | 0.777 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| Japan (Tokyo) | 0.663 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| South Africa (Cape town) | 0.649 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| US West (N. California) | 0.507 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| US West (Oregon) | 0.466 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| US Midwest (Ohio) | 0.354 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| Canada (Monreal, Quebec) | 0.347 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| US East (Northern Virginia) | 0.286 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 | |
| Europe (London) | 0.061 | UP | 155.133.132.6 webacc4.sd3.ghst.net | Paris, Île-de-France, France | 200 |
Checkpoint — A server located in a specific region that checks connectivity with your URL.
Time — How many seconds it took the checkpoint to receive a response from your URL for an HTTP GET request.
Status — UP if the checkpoint received HTTP response code 200; DOWN if the response code is anything other than HTTP 200.
Time — How many seconds it took the checkpoint to receive a response from your URL for an HTTP GET request.
Status — UP if the checkpoint received HTTP response code 200; DOWN if the response code is anything other than HTTP 200.
No data found
Make sure you are testing the correct URL and that the server is properly responding to all requests.
Make sure you are testing the correct URL and that the server is properly responding to all requests.