`districtweddings.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	`ns29.domaincontrol.com` ⭐
		A	2603:5:2181::f^{🇺🇸 GODADDY-DNS2603:5:2180::/44}
			PTR	`ns29.domaincontrol.com`
		A	97.74.104.15^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns29.domaincontrol.com`
NS	`ns30.domaincontrol.com`
		A	2603:5:2281::f^{🇺🇸 GODADDY-DNS2603:5:2280::/44}
			PTR	`ns30.domaincontrol.com`
		A	173.201.72.15^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns30.domaincontrol.com`
SOA	`ns29.domaincontrol.com`dns@jomax.net 2026-03-02 #1

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

Same first word

districtweddings.com

DNS History

9 records (4 active, 5 former)

○NSns1.bluehost.com2015-07-26 → 2017-03-23 · 4 obs

● 2015-07-26 09:32:00
● 2017-03-23 15:47:52
○ 2026-05-02 07:59:06
○ 2026-07-19 08:26:06

○NSns2.bluehost.com2015-07-26 → 2017-03-23 · 4 obs

● 2015-07-26 09:32:00
● 2017-03-23 15:47:52
○ 2026-05-02 07:59:06
○ 2026-07-19 08:26:06

●NSns29.domaincontrol.com2026-05-02 → 2026-07-19 · 3 obs

○ 2017-03-23 15:47:52
● 2026-05-02 07:59:06
● 2026-07-19 08:26:06

●NSns30.domaincontrol.com2026-05-02 → 2026-07-19 · 3 obs

○ 2017-03-23 15:47:52
● 2026-05-02 07:59:06
● 2026-07-19 08:26:06

○MXmail.districtweddings.com2015-07-26 → 2017-03-23 · 4 obs

● 2015-07-26 09:32:00
● 2017-03-23 15:47:52
○ 2026-05-02 07:59:06
○ 2026-07-19 08:26:06

●A15.197.225.1282026-05-02 → 2026-07-19 · 3 obs

○ 2017-03-23 15:47:52
● 2026-05-02 07:59:06
● 2026-07-19 08:26:06

●A3.33.251.1682026-05-02 → 2026-07-19 · 3 obs

○ 2017-03-23 15:47:52
● 2026-05-02 07:59:06
● 2026-07-19 08:26:06

○A66.147.242.852015-07-26 → 2016-03-14 · 4 obs

● 2015-07-26 09:32:00
● 2016-03-14 08:26:10
○ 2016-07-09 22:20:30
○ 2026-07-19 08:26:06

○A66.147.244.2362016-07-09 → 2017-03-23 · 5 obs

○ 2016-03-14 08:26:10
● 2016-07-09 22:20:30
● 2017-03-23 15:47:52
○ 2026-05-02 07:59:06
○ 2026-07-19 08:26:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
districtweddings.com	ns29.domaincontrol.com, ns30.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.72.15

NS records: ns29.domaincontrol.com, ns30.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for districtweddings.com (unsigned zone)

⏱️ Timing

Total: 126ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns29.domaincontrol.com, ns29.domaincontrol.com, ns30.domaincontrol.com...)

Analysis

IP Addresses

districtweddings.com resolves to the IP addresses 3.33.251.168 and 15.197.225.128

oraclecommissionslawsuit.com, aee.us, vitabits.net plus two other host names have IP numbers in common with districtweddings.com.

Name Servers

districtweddings.com is served by two delegated name servers, ns29.domaincontrol.com and ns30.domaincontrol.com.

The name server configuration of districtweddings.com is shared with other domains, for instance sofuture.club, myorganizher.com, oliverbuilding.com and two others.

Each of the two host names carries two IP addresses: ns29.domaincontrol.com points to 97.74.104.15 and 2603:5:2181::f, and ns30.domaincontrol.com points to 173.201.72.15 and 2603:5:2281::f.

districtweddings.com - robtex.com