Boringregions.com Reviews
Boringregions.com has a total of 7 DNS records. In the server records, it appears to be registered with the IP address 104.18.0.144 in Canada, Ontario, Toronto, America/Toronto with the information belonging to Cloudflare, Inc. The domain was registered on N/A, and the expiration date appears to be on N/A. When checked on , the website is still online. According to Siteadvisor, visiting boringregions.com is safe.
Location :
Toronto, Canada 🇨🇦
Last Checked: January 10, 2025
Server Status :
Online
Last Checked: January 10, 2025
Server :
Cloudflare, Inc.
Last Checked: January 10, 2025
Robot.txt Information
| Robot | Path | Permission |
|---|---|---|
| Google Bot | / | |
| Bing Bot | / | |
| Baudi Spider | / | |
| Yandex Bot | / |
Meta Tags
| Title | Welcome to nginx! |
| Description | N/A |
| Keywords | N/A |
Server Information
| Website | boringregions.com |
| Host IP | 104.18.0.144 🇨🇦 |
| Location | Toronto, Canada |
Similar Sites
General Info - Legit or Scam?
| Created | N/A |
| Expires | N/A |
| Owner | N/A |
| Hosting Company | Cloudflare, Inc. |
| Registrar | N/A |
| IPs | 104.18.0.144 |
| DNS |
|
DNS Records
| Host | Type | TTL | Data |
|---|---|---|---|
| boringregions.com | A | 300 | IP/Target: 104.18.0.144 |
| boringregions.com | A | 300 | IP/Target: 104.18.1.144 |
| boringregions.com | NS | 86400 | Target: woz.ns.cloudflare.com |
| boringregions.com | NS | 86400 | Target: bingo.ns.cloudflare.com |
| boringregions.com | SOA | 1800 |
MNAME: bingo.ns.cloudflare.com RNAME: dns.cloudflare.com Serial: 2361351419 Refresh: 10000 Retry: 2400 Expire: 604800 Minimum TTL: 1800 |
| boringregions.com | AAAA | 300 | Ipv6: 2606:4700::6812:90 |
| boringregions.com | AAAA | 300 | Ipv6: 2606:4700::6812:190 |
HTTP Headers
0: HTTP/1.1 200 OK
Date: Fri, 10 Jan 2025 03:02:04 GMT
Content-Type: text/html
Connection: close
Last-Modified: Tue, 21 Apr 2020 14:09:01 GMT
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 8ff96d145c6c7740-AMS
|
Boringregions.com Whois Information
Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date.
|