`microsoftfamily.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`
SOA	`ns1.atom.com`hostmaster@microsoftfamily.com 2026-07-17 #3

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

Same first word

microsoftfamily.com

DNS History

10 records (3 active, 7 former)

●NSns1.atom.com2026-07-19 → 2026-08-01 · 3 obs

○ 2017-12-19 20:45:40
● 2026-07-19 22:45:52
● 2026-08-01 13:27:16

●NSns2.atom.com2026-07-19 → 2026-08-01 · 3 obs

○ 2017-12-19 20:45:40
● 2026-07-19 22:45:52
● 2026-08-01 13:27:16

○NSns47.domaincontrol.com2016-12-30 → 2017-12-19 · 5 obs

○ 2016-04-29 14:28:44
● 2016-12-30 05:05:50
● 2017-12-19 20:45:40
○ 2026-07-19 22:45:52
○ 2026-08-01 13:27:16

○NSns48.domaincontrol.com2016-12-30 → 2017-12-19 · 5 obs

○ 2016-04-29 14:28:44
● 2016-12-30 05:05:50
● 2017-12-19 20:45:40
○ 2026-07-19 22:45:52
○ 2026-08-01 13:27:16

○NSpdns05.domaincontrol.com2015-06-29 → 2016-04-29 · 4 obs

● 2015-06-29 01:45:36
● 2016-04-29 14:28:44
○ 2016-12-30 05:05:50
○ 2026-08-01 13:27:16

○NSpdns06.domaincontrol.com2015-06-29 → 2016-04-29 · 4 obs

● 2015-06-29 01:45:36
● 2016-04-29 14:28:44
○ 2016-12-30 05:05:50
○ 2026-08-01 13:27:16

○MXmailstore1.secureserver.net2015-06-29 → 2017-12-19 · 4 obs

● 2015-06-29 01:45:36
● 2017-12-19 20:45:40
○ 2026-07-19 22:45:52
○ 2026-08-01 13:27:16

○MXsmtp.secureserver.net2015-06-29 → 2017-12-19 · 4 obs

● 2015-06-29 01:45:36
● 2017-12-19 20:45:40
○ 2026-07-19 22:45:52
○ 2026-08-01 13:27:16

○A184.168.221.532015-06-29 → 2017-12-19 · 4 obs

● 2015-06-29 01:45:36
● 2017-12-19 20:45:40
○ 2026-07-19 22:45:52
○ 2026-08-01 13:27:16

●A52.20.84.622026-07-19 → 2026-08-01 · 3 obs

○ 2017-12-19 20:45:40
● 2026-07-19 22:45:52
● 2026-08-01 13:27:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
microsoftfamily.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 microsoftfamily.com (unsigned zone)

⏱️ Timing

Total: 3045ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

microsoftfamily.com resolves to one IP address: 52.20.84.62.

jufh.com, digitalmohawk.com, rolozo.com and two other host names share IP numbers with microsoftfamily.com.

Name Servers

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

microsoftfamily.com uses the same name servers as several other domains — among them zoox.app, teamaura.com, beyondgoogle.com and two more.

microsoftfamily.com has at least partial name server overlap with other domains, such as arab9.com, dirtquads.com, erfaq.com and two others.

It is common to see these name servers used together with name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn and verification-4vpzyw6zhpagmhwxhhsokh.ns101.verify.hn.

ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.

microsoftfamily.com - robtex.com