`indianapolisrecord.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns37.domaincontrol.com` ⭐
		A	2603:5:21c1::13^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns37.domaincontrol.com`
		A	97.74.108.19^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns37.domaincontrol.com`
NS	`ns38.domaincontrol.com`
		A	2603:5:22c1::13^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns38.domaincontrol.com`
		A	173.201.76.19^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns38.domaincontrol.com`
SOA	`ns37.domaincontrol.com`dns@jomax.net 2023-09-19 #0

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

Same first word

indianapolisrecord.com

DNS History

10 records (4 active, 6 former)

●NSns37.domaincontrol.com2026-04-04 → 2026-04-27 · 3 obs

○ 2017-12-09 19:33:20
● 2026-04-04 18:26:48
● 2026-04-27 18:28:48

●NSns38.domaincontrol.com2026-04-04 → 2026-04-27 · 3 obs

○ 2017-12-09 19:33:20
● 2026-04-04 18:26:48
● 2026-04-27 18:28:48

○NSredbusprimarydns.indianapolisrecord.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

○NSredbussecondarydns.indianapolisrecord.com2016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

●A15.197.148.332026-04-04 → 2026-04-27 · 3 obs

○ 2017-12-09 19:33:20
● 2026-04-04 18:26:48
● 2026-04-27 18:28:48

○A195.149.84.1002016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

○A195.149.84.1012016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

○A2001:67c:38c::642016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

○A2001:67c:38c::652016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 18:59:12
○ 2017-12-09 19:33:20
○ 2026-04-27 18:28:48

●A3.33.130.1902026-04-04 → 2026-04-27 · 3 obs

○ 2017-12-09 19:33:20
● 2026-04-04 18:26:48
● 2026-04-27 18:28:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
indianapolisrecord.com	ns37.domaincontrol.com, ns38.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.108.19

NS records: ns37.domaincontrol.com, ns38.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for indianapolisrecord.com (unsigned zone)

⏱️ Timing

Total: 94ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns37.domaincontrol.com, ns38.domaincontrol.com`
SOA	1	`ns37.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns37.domaincontrol.com, ns37.domaincontrol.com, ns38.domaincontrol.com...)

Analysis

IP Addresses

indianapolisrecord.com resolves to two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names, for instance niftyd.com, nelson-brothers.com, mileagequest.com, yamoussabangoura.com and hendrixenergy.com share IP numbers with indianapolisrecord.com.

Name Servers

indianapolisrecord.com has two name servers: ns37.domaincontrol.com and ns38.domaincontrol.com.

indianapolisrecord.com shares the same name server setup as other domains, for example electricianscharlottenc.net, electricianhillsborough.com, srstaffing.com, lif3.net and shadowstar.me.

indianapolisrecord.com partially shares name servers with other domains, for instance omnipropertycos.com.

Host names with two IP numbers:

ns37.domaincontrol.com points to: 2603:5:21c1::13 and 97.74.108.19; ns38.domaincontrol.com points to: 2603:5:22c1::13 and 173.201.76.19.

indianapolisrecord.com - robtex.com