`weddingplaning.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.namefind.com` ⭐
		A	97.74.99.64^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.namefind.com`
NS	`ns2.namefind.com`
		A	173.201.67.64^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.namefind.com`
TXT	`v=spf1 -all`
SOA	`ns1.namefind.com`dns@jomax.net 2023-03-15 #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=1774420272

Same first word

weddingplaning.com

DNS History

11 records (4 active, 7 former)

○NSbuy.internettraffic.com2015-07-02 → 2016-05-04 · 4 obs

● 2015-07-02 12:14:16
● 2016-05-04 05:08:08
○ 2017-06-25 14:16:12
○ 2026-03-25 06:34:08

●NSns1.namefind.com2026-03-20 → 2026-03-25 · 3 obs

○ 2017-06-25 14:16:12
● 2026-03-20 19:26:24
● 2026-03-25 06:34:08

○NSns1.uniregistrymarket.link2017-06-25 → 2017-06-25 · 4 obs

○ 2016-05-04 05:08:08
● 2017-06-25 14:16:12
○ 2026-03-20 19:26:24
○ 2026-03-25 06:34:08

●NSns2.namefind.com2026-03-20 → 2026-03-25 · 3 obs

○ 2017-06-25 14:16:12
● 2026-03-20 19:26:24
● 2026-03-25 06:34:08

○NSns2.uniregistrymarket.link2017-06-25 → 2017-06-25 · 4 obs

○ 2016-05-04 05:08:08
● 2017-06-25 14:16:12
○ 2026-03-20 19:26:24
○ 2026-03-25 06:34:08

○NSsell.internettraffic.com2015-07-02 → 2016-05-04 · 4 obs

● 2015-07-02 12:14:16
● 2016-05-04 05:08:08
○ 2017-06-25 14:16:12
○ 2026-03-25 06:34:08

●A13.248.169.482026-03-20 → 2026-03-25 · 3 obs

○ 2017-06-25 14:16:12
● 2026-03-20 19:26:24
● 2026-03-25 06:34:08

○A176.74.176.1862016-05-04 → 2016-05-04 · 4 obs

○ 2016-01-27 09:02:48
● 2016-05-04 05:08:08
○ 2017-06-25 14:16:12
○ 2026-03-25 06:34:08

○A69.172.201.1532017-06-25 → 2017-06-25 · 4 obs

○ 2016-05-04 05:08:08
● 2017-06-25 14:16:12
○ 2026-03-20 19:26:24
○ 2026-03-25 06:34:08

○A69.172.201.2082015-07-02 → 2016-01-27 · 4 obs

● 2015-07-02 12:14:16
● 2016-01-27 09:02:48
○ 2016-05-04 05:08:08
○ 2026-03-25 06:34:08

●A76.223.54.1462026-03-20 → 2026-03-25 · 3 obs

○ 2017-06-25 14:16:12
● 2026-03-20 19:26:24
● 2026-03-25 06:34:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
weddingplaning.com	ns2.namefind.com, ns1.namefind.com	2 records

✅ Authoritative Response

Server:173.201.67.64

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingplaning.com (unsigned zone)

⏱️ Timing

Total: 142ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.248.169.48, 76.223.54.146`
NS	2	`ns1.namefind.com, ns2.namefind.com`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.namefind.com dns.jomax.net`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

weddingplaning.com resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.

other host names including freshpoint.org, chartertrek.com, bafe.co, getslimforlife.com and 6apart.www.appliancesconnections.com share IP numbers with weddingplaning.com.

Name Servers

weddingplaning.com is delegated to two name servers ns1.namefind.com and ns2.namefind.com.

weddingplaning.com shares the same name server setup as other domains, for instance 295.co.uk, amcforums.com, arabheavy.com, bos-ns1.bos.actionmanage.com and hostmaster.displayweb.com.

weddingplaning.com at least partially shares name servers with other domains, for instance woxot.com.

these name servers are commonly used alongside verification-gsjsth52a2zvxihb6hoygp.ns101.verify.hn.

Host names with one IP number:

ns1.namefind.com points to 97.74.99.64

ns2.namefind.com points to 173.201.67.64

weddingplaning.com - robtex.com