`corridorsummit.com`

DNSSEC	⚠️ Not signed
A	15.157.142.49^{🇨🇦 Amazon15.156.0.0/15 EC2 YUL prefix}
		PTR	`ec2-15-157-142-49.ca-central-1.compute.amazonaws.com`
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com` ⚠️ Not in parent delegation
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
SOA	`ns1.digitalocean.com`hostmaster@corridorsummit.com serial=1745954865

`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.net`nstld@verisign-grs.com serial=1774667812

Same first word

corridorsummit.com

DNS History

5 records (4 active, 1 former)

●NSns1.digitalocean.com2018-05-07 → 2026-03-28 · 2 obs

● 2018-05-07 01:36:16
● 2026-03-28 03:36:00

●NSns2.digitalocean.com2018-05-07 → 2026-03-28 · 2 obs

● 2018-05-07 01:36:16
● 2026-03-28 03:36:00

●NSns3.digitalocean.com2018-05-07 → 2026-03-28 · 2 obs

● 2018-05-07 01:36:16
● 2026-03-28 03:36:00

●A15.157.142.492026-03-28 → 2026-03-28 · 3 obs

○ 2018-05-07 01:36:16
● 2026-03-28 03:35:58
● 2026-03-28 03:36:00

○A159.203.11.752018-05-07 → 2018-05-07 · 3 obs

● 2018-05-07 01:36:16
○ 2026-03-28 03:35:58
○ 2026-03-28 03:36:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net...	-
corridorsummit.com	ns1.digitalocean.com, ns2.digitalocean.com	2 records

✅ Authoritative Response

Server:172.64.53.21

NS records: ns1.digitalocean.com, ns2.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for corridorsummit.com (unsigned zone)

⏱️ Timing

Total: 2254ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`15.157.142.49`
NS	3	`ns2.digitalocean.com, ns3.digitalocean.com...`
SOA	1	`ns1.digitalocean.com hostmaster.corridor`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.digitalocean.com, ns2.digitalocean.com)

Analysis

IP Addresses

corridorsummit.com points to a single IP: 15.157.142.49.

Other host names such as ec2-15-157-142-49.ca-central-1.compute.amazonaws.com and lrtready.com share IP numbers with corridorsummit.com.

Name Servers

corridorsummit.com is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

corridorsummit.com partially shares name servers with other domains; examples include thepeterstone.com, eduges.com.gt, 132.230.157.in-addr.arpa, mdcwebdesign.com and minify.in.

Host names with two IP numbers:

ns1.digitalocean.com points to 2606:4700:52::ac40:34d2 and 172.64.52.210.

ns2.digitalocean.com points to 2606:4700:5a::ac40:3515 and 172.64.53.21.

ns3.digitalocean.com points to 2606:4700:52::ac40:31d1 and 172.64.49.209.

corridorsummit.com - robtex.com