corridorly.com - dns.ninja
corridorly.com
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=1784390977 | ||||||
Subdomains
dev.corridorly.com |
Same first word
corridorly.com |
DNS History
6 records (6 active, 0 former)
●NSns-1349.awsdns-40.org2026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
●NSns-1861.awsdns-40.co.uk2026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
●NSns-423.awsdns-52.com2026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
●NSns-642.awsdns-16.net2026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
●MXsmtp.google.com2026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
●A216.150.1.12026-07-18 → 2026-07-18 · 2 obs
● 2026-07-18 16:12:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net... | - |
| corridorly.com | ns-642.awsdns-16.net, ns-423.awsdns-52.com, ns-1861.awsdns-40.co.uk, ns-1349.awsdns-40.org | 2 records |
✅ Authoritative Response
Server:205.251.194.130
NS records: ns-642.awsdns-16.net, ns-423.awsdns-52.com, ns-1861.awsdns-40.co.uk, ns-1349.awsdns-40.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for corridorly.com (unsigned zone)
⏱️ Timing
Total: 2299ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.150.1.1 |
| NS | 4 | ns-1349.awsdns-40.org, ns-1861.awsdns-40.co.uk... |
| MX | 1 | smtp.google.com (pri: 1) |
| TXT | 1 | google-site-verification=gCR5-7KUGIO5b-I |
| SOA | 1 | ns-423.awsdns-52.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-423.awsdns-52.com, ns-423.awsdns-52.com)
Analysis
Hierarchy
dev.corridorly.com is delegated beneath corridorly.com.
IP Addresses
corridorly.com resolves to just one IP address, 216.150.1.1.
Two other host names, along with kensei.one, orthodonticexcellence.co.uk and wearecrank.com, also share IP numbers with corridorly.com.
Name Servers
The NS records for corridorly.com point to four name servers: ns-423.awsdns-52.com, ns-642.awsdns-16.net, ns-1349.awsdns-40.org and ns-1861.awsdns-40.co.uk.
There is at least partial name server overlap between corridorly.com and other domains — drk4jud2qmtln.cloudfront.net, lompocleakdetection.com, ftrace.de and two more among them.
All four hostnames — ns-423.awsdns-52.com, ns-642.awsdns-16.net, ns-1349.awsdns-40.org and ns-1861.awsdns-40.co.uk — resolve to two IP numbers apiece: ns-423.awsdns-52.com to 205.251.193.167 and 2600:9000:5301:a700::1; ns-642.awsdns-16.net to 205.251.194.130 and 2600:9000:5302:8200::1; ns-1349.awsdns-40.org to 205.251.197.69 and 2600:9000:5305:4500::1; ns-1861.awsdns-40.co.uk to 205.251.199.69 and 2600:9000:5307:4500::1.
Mail Servers
The sole mail server for corridorly.com is smtp.google.com.
Among the domains sharing a mail server setup with corridorly.com are gcenturion.com, sibar.in, bcf-group.com and two others.
There is at least a partial MX overlap between corridorly.com and other domains, including vimschool.com, ubnsoft.com, bejege.com and two others.
With 9 IP addresses total, smtp.google.com resolves to 142.251.167.27, 172.253.62.27, 172.253.139.27 and 6 others.