`beachfrontwedding.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=1776018052

Subdomains

nullmx.beachfrontwedding.com

Same first word

beachfrontwedding.com

DNS History

10 records (4 active, 6 former)

○NSbuy.internettraffic.com2015-08-01 → 2016-03-31 · 4 obs

● 2015-08-01 04:09:28
● 2016-03-31 06:06:18
○ 2016-09-19 14:54:00
○ 2026-04-12 18:34:14

●NSns1.namefind.com2026-04-12 → 2026-04-12 · 3 obs

○ 2017-05-19 20:53:40
● 2026-04-12 11:47:18
● 2026-04-12 18:34:14

○NSns1.uniregistrymarket.link2016-09-19 → 2017-05-19 · 5 obs

○ 2016-03-31 06:06:18
● 2016-09-19 14:54:00
● 2017-05-19 20:53:40
○ 2026-04-12 11:47:18
○ 2026-04-12 18:34:14

●NSns2.namefind.com2026-04-12 → 2026-04-12 · 3 obs

○ 2017-05-19 20:53:40
● 2026-04-12 11:47:18
● 2026-04-12 18:34:14

○NSns2.uniregistrymarket.link2016-09-19 → 2017-05-19 · 5 obs

○ 2016-03-31 06:06:18
● 2016-09-19 14:54:00
● 2017-05-19 20:53:40
○ 2026-04-12 11:47:18
○ 2026-04-12 18:34:14

○NSsell.internettraffic.com2015-08-01 → 2016-03-31 · 4 obs

● 2015-08-01 04:09:28
● 2016-03-31 06:06:18
○ 2016-09-19 14:54:00
○ 2026-04-12 18:34:14

●A13.248.169.482026-04-12 → 2026-04-12 · 3 obs

○ 2017-05-19 20:53:40
● 2026-04-12 11:47:18
● 2026-04-12 18:34:14

○A69.172.201.1532016-09-19 → 2017-05-19 · 5 obs

○ 2016-03-31 06:06:18
● 2016-09-19 14:54:00
● 2017-05-19 20:53:40
○ 2026-04-12 11:47:18
○ 2026-04-12 18:34:14

○A69.172.201.2082015-08-01 → 2016-03-31 · 4 obs

● 2015-08-01 04:09:28
● 2016-03-31 06:06:18
○ 2016-09-19 14:54:00
○ 2026-04-12 18:34:14

●A76.223.54.1462026-04-12 → 2026-04-12 · 3 obs

○ 2017-05-19 20:53:40
● 2026-04-12 11:47:18
● 2026-04-12 18:34:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net...	-
beachfrontwedding.com	ns2.namefind.com, ns1.namefind.com	2 records

✅ Authoritative Response

Server:97.74.99.64

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for beachfrontwedding.com (unsigned zone)

⏱️ Timing

Total: 90ms | 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

Hierarchy

beachfrontwedding.com is the parent of nullmx.beachfrontwedding.com.

IP Addresses

The entity beachfrontwedding.com points to two IP numbers: 13.248.169.48 and 76.223.54.146.

For instance, other host names nmks.com, hdk.drmpod.com, smx.email, gwmail02.oysterfunds.com and hist.org share IP numbers with beachfrontwedding.com.

Name Servers

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

beachfrontwedding.com uses the same name server setup as other domains such as n77n.com, hostmaster.datus.net, nullmx.dublinvcc.com, mail.corporationwebs.com and mx4.resgate.net.

beachfrontwedding.com shares name servers with other domains at least partially, for example connecting.us.

Host names with one IP number:

ns1.namefind.com points to: 97.74.99.64.

ns2.namefind.com points to: 173.201.67.64.

beachfrontwedding.com - robtex.com