corridorwatch.com - dns.ninja
corridorwatch.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.96.162.143🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc. | ||||||
| PTR | 143.162.96.66.static.eigbox.net | ||||||
| NS | ns1.domain.com ⭐ | ||||||
| A | 172.64.52.73🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.domain.com | ||||||
| A | 172.64.53.117🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| MX | mx.corridorwatch.com ⭐ | ||||||
| A | 66.96.140.164🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc. | ||||||
| PTR | 164.140.96.66.static.eigbox.net | ||||||
| A | 66.96.140.165🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc. | ||||||
| PTR | 165.140.96.66.static.eigbox.net | ||||||
| TXT | v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all | ||||||
| SOA | NS1.DOMAIN.comdnsadmin@domain@com serial=124033119 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785624697 | ||||||
Subdomains
Same first word
corridorwatch.com |
corridorwatch.net |
Similar names
DNS History
9 records (4 active, 5 former)
○NSns1.cqhost.com2015-08-20 → 2017-03-25 · 4 obs
● 2017-03-25 13:51:42
○ 2020-01-04 02:28:02
○ 2026-08-01 23:12:16
●NSns1.domain.com2020-01-04 → 2026-08-01 · 3 obs
● 2020-01-04 02:28:02
● 2026-08-01 23:12:16
○NSns2.cqhost.com2015-08-20 → 2017-03-25 · 4 obs
● 2017-03-25 13:51:42
○ 2020-01-04 02:28:02
○ 2026-08-01 23:12:16
●NSns2.domain.com2020-01-04 → 2026-08-01 · 3 obs
● 2020-01-04 02:28:02
● 2026-08-01 23:12:16
○MXmail.corridorwatch.com2015-08-20 → 2017-03-25 · 4 obs
● 2017-03-25 13:51:42
○ 2020-01-04 02:28:02
○ 2026-08-01 23:12:16
●MXmx.corridorwatch.com2020-01-04 → 2026-08-01 · 3 obs
● 2020-01-04 02:28:02
● 2026-08-01 23:12:16
○A149.56.120.2312016-06-29 → 2017-03-25 · 5 obs
● 2016-06-29 17:40:40
● 2017-03-25 13:51:42
○ 2020-01-04 02:28:02
○ 2026-08-01 23:12:16
●A66.96.162.1432020-01-04 → 2026-08-01 · 3 obs
● 2020-01-04 02:28:02
● 2026-08-01 23:12:16
○A70.47.219.702015-08-20 → 2016-03-16 · 4 obs
● 2016-03-16 09:53:26
○ 2016-06-29 17:40:40
○ 2026-08-01 23:12:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| corridorwatch.com | ns2.domain.com, ns1.domain.com | 2 records |
✅ Authoritative Response
Server:172.64.53.117
NS records: ns2.domain.com, ns1.domain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for corridorwatch.com (unsigned zone)
⏱️ Timing
Total: 235ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.96.162.143 |
| NS | 2 | ns2.domain.com, ns1.domain.com |
| MX | 1 | mx.corridorwatch.com (pri: 30) |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 include:websit |
| SOA | 1 | NS1.DOMAIN.com dnsadmin@domain.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.domain.com, ns1.domain.com)
Analysis
Hierarchy
The parent domain of mail.corridorwatch.com and mx.corridorwatch.com is corridorwatch.com.
IP Addresses
corridorwatch.com directs to one IP number, which is 66.96.162.143.
Among the host names that share IP numbers with corridorwatch.com are asianartguru.com, seaturtletravel.com, charcocontractors.com and two others.
Name Servers
Two name servers handle the delegation for corridorwatch.com: ns1.domain.com and ns2.domain.com.
corridorwatch.com has the same name server delegation as a number of other domains, such as hinghamlawnmowing.com, anonymous-liberty.com, gradito.com and two more.
The name servers of corridorwatch.com overlap at least partially with those of other domains — among them hcmboard.com, lordfilm-behead.ru, releasethehoundsinc.com and two more.
These name servers are routinely co-deployed with the name servers ns3.domain.com, ns1.yourhostingaccount.com, ns2.yourhostingaccount.com and two others.
Both ns1.domain.com and ns2.domain.com have a single IP address each — ns1.domain.com resolves to 172.64.52.73 while ns2.domain.com resolves to 172.64.53.117.
Mail Servers
corridorwatch.com routes its mail through a single mail server, mx.corridorwatch.com.
mx.corridorwatch.com resolves to two IP numbers — 66.96.140.164 and 66.96.140.165.