`burlingtoncollision.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns67.domaincontrol.com` ⭐
		A	2603:5:2174::2c^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns67.domaincontrol.com`
		A	97.74.103.44^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns67.domaincontrol.com`
NS	`ns68.domaincontrol.com`
		A	2603:5:2274::2c^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns68.domaincontrol.com`
		A	173.201.71.44^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns68.domaincontrol.com`
SOA	`ns67.domaincontrol.com`dns@jomax.net 2025-10-15 #3

`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=1774522407

Same first word

burlingtoncollision.com

DNS History

5 records (4 active, 1 former)

●NSns67.domaincontrol.com2019-12-26 → 2026-03-26 · 2 obs

● 2019-12-26 17:32:50
● 2026-03-26 10:58:06

●NSns68.domaincontrol.com2019-12-26 → 2026-03-26 · 2 obs

● 2019-12-26 17:32:50
● 2026-03-26 10:58:06

●A15.197.225.1282026-02-25 → 2026-03-26 · 3 obs

○ 2019-12-26 17:32:50
● 2026-02-25 11:08:20
● 2026-03-26 10:58:06

○A184.168.131.2412019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:32:50
○ 2026-02-25 11:08:20
○ 2026-03-26 10:58:06

●A3.33.251.1682026-02-25 → 2026-03-26 · 3 obs

○ 2019-12-26 17:32:50
● 2026-02-25 11:08:20
● 2026-03-26 10:58:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...	-
burlingtoncollision.com	ns67.domaincontrol.com, ns68.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.71.44

NS records: ns67.domaincontrol.com, ns68.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for burlingtoncollision.com (unsigned zone)

⏱️ Timing

Total: 237ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns67.domaincontrol.com, ns68.domaincontrol.com`
SOA	1	`ns67.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)

Analysis

IP Addresses

burlingtoncollision.com points to two IPs: 3.33.251.168 and 15.197.225.128.

Other host names including mgcsas.com, siasindia.com, purduestartupfoundry.com, reverselogisticstrends.com and op(0x6d696c66)am.org share IP numbers with burlingtoncollision.com.

Name Servers

burlingtoncollision.com's delegation uses two name servers, ns67.domaincontrol.com and ns68.domaincontrol.com.

burlingtoncollision.com shares the same name server setup as other domains, for example egmlog.com, iscenethat.com, ftmyersrentals.net, twm.email and pacificlogisticsllc.com.

Host names with two IPs:

ns67.domaincontrol.com points to: 2603:5:2174::2c and 97.74.103.44

ns68.domaincontrol.com points to: 2603:5:2274::2c and 173.201.71.44

burlingtoncollision.com - robtex.com