`weddingcollection.com`

DNSSEC	⚠️ Not signed
A	52.20.84.62^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
		PTR	`ec2-52-20-84-62.compute-1.amazonaws.com`
NS	`ns1.atom.com` ⭐
		A	44.219.81.145^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-219-81-145.compute-1.amazonaws.com`
NS	`ns2.atom.com`
		A	50.19.240.86^{🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix}
			PTR	`ec2-50-19-240-86.compute-1.amazonaws.com`
TXT	`f0095018235b8109a2bf9f65674a1784b6971ed6`
SOA	`ns1.atom.com`hostmaster@weddingcollection.com 2025-10-27 #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=1771291435

Same first word

weddingcollection.com

DNS History

11 records (3 active, 8 former)

○NSbuy.internettraffic.com2015-06-09 → 2016-04-05 · 5 obs

○ 2008-03-20 09:02:02
● 2015-06-09 20:33:30
● 2016-04-05 18:55:02
○ 2016-11-08 16:30:04
○ 2026-03-24 11:58:44

●NSns1.atom.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-06-02 14:21:42
● 2026-03-24 11:58:44

○NSns1.smartname.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 09:02:02
○ 2015-06-09 20:33:30
○ 2026-03-24 11:58:44

○NSns1.uniregistrymarket.link2016-11-08 → 2017-06-02 · 4 obs

○ 2016-04-05 18:55:02
● 2016-11-08 16:30:04
● 2017-06-02 14:21:42
○ 2026-03-24 11:58:44

●NSns2.atom.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-06-02 14:21:42
● 2026-03-24 11:58:44

○NSns2.smartname.com2008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 09:02:02
○ 2015-06-09 20:33:30
○ 2026-03-24 11:58:44

○NSns2.uniregistrymarket.link2016-11-08 → 2017-06-02 · 4 obs

○ 2016-04-05 18:55:02
● 2016-11-08 16:30:04
● 2017-06-02 14:21:42
○ 2026-03-24 11:58:44

○NSsell.internettraffic.com2015-06-09 → 2016-04-05 · 5 obs

○ 2008-03-20 09:02:02
● 2015-06-09 20:33:30
● 2016-04-05 18:55:02
○ 2016-11-08 16:30:04
○ 2026-03-24 11:58:44

●A52.20.84.622026-03-24 → 2026-03-24 · 2 obs

○ 2017-06-02 14:21:42
● 2026-03-24 11:58:44

○A69.172.201.1532016-11-08 → 2017-06-02 · 4 obs

○ 2016-04-05 18:55:02
● 2016-11-08 16:30:04
● 2017-06-02 14:21:42
○ 2026-03-24 11:58:44

○A69.172.201.2082015-06-09 → 2016-04-05 · 5 obs

○ 2008-03-20 09:02:02
● 2015-06-09 20:33:30
● 2016-04-05 18:55:02
○ 2016-11-08 16:30:04
○ 2026-03-24 11:58:44

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:44.219.81.145

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingcollection.com (unsigned zone)

⏱️ Timing

Total: 3144ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.20.84.62`
NS	2	`ns2.atom.com, ns1.atom.com`
TXT	1	`f0095018235b8109a2bf9f65674a1784b6971ed6`
SOA	1	`ns1.atom.com hostmaster.weddingcollectio`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

weddingcollection.com points to a single IP address: 52.20.84.62.

Other host names such as (0x787878)homemovies.com, nomgo.com, dvdlots.com, mir.wiki and logicalstory.com share IP numbers with weddingcollection.com.

Name Servers

weddingcollection.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.

weddingcollection.com uses the same name server setup as other domains, including japanlife.net, huhhah.com, jabbed.com, hackathon.nyc and eovon.com.

weddingcollection.com at least partially shares name servers with other domains; for instance datingmogul.com, tradinghubs.com and viamotive.com.

Hostnames with a single IP

ns1.atom.com resolves to: 44.219.81.145.

ns2.atom.com resolves to: 50.19.240.86.

weddingcollection.com - robtex.com