2binary.com - dns.ninja

`2binary.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@2binary.com 2024-11-18 #2

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

Same first word

2binary.com

DNS History

13 records (3 active, 10 former)

○NSdns31.hichina.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-13 08:27:34
● 2019-12-30 11:52:40
○ 2026-03-22 15:26:34
○ 2026-07-31 00:02:36

○NSdns32.hichina.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-13 08:27:34
● 2019-12-30 11:52:40
○ 2026-03-22 15:26:34
○ 2026-07-31 00:02:36

○NSns1.aplus.net2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

●NSns1.atom.com2026-03-22 → 2026-07-31 · 3 obs

○ 2019-12-30 11:52:40
● 2026-03-22 15:26:34
● 2026-07-31 00:02:36

○NSns2.aplus.net2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

●NSns2.atom.com2026-03-22 → 2026-07-31 · 3 obs

○ 2019-12-30 11:52:40
● 2026-03-22 15:26:34
● 2026-07-31 00:02:36

○NSns3.aplus.net2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

○MXmx1c40.carrierzone.com2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

○MXmx2c40.carrierzone.com2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

○MXmx3c40.carrierzone.com2015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

○A45.196.121.1642019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-13 08:27:34
● 2019-12-30 11:52:40
○ 2026-03-22 15:26:34
○ 2026-07-31 00:02:36

●A52.20.84.622026-03-22 → 2026-07-31 · 3 obs

○ 2019-12-30 11:52:40
● 2026-03-22 15:26:34
● 2026-07-31 00:02:36

○A64.29.151.2212015-06-04 → 2017-03-13 · 4 obs

● 2015-06-04 12:56:20
● 2017-03-13 08:27:34
○ 2019-12-30 11:52:40
○ 2026-07-31 00:02:36

🔍 DNS Trace

📋 Delegation Chain

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

⏱️ Timing

Total: 3100ms | 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.2binary.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

2binary.com resolves to one IP address: 52.20.84.62.

www.rms.ae, juuba.com, evejo.com and two other host names share IP numbers with 2binary.com.

Name Servers

The NS records for 2binary.com delegate to ns1.atom.com and ns2.atom.com.

2binary.com uses the same name servers as several other domains — among them nela.es, 546.us, frby.com and two more.

The name servers for 2binary.com are at least partly shared with other domains such as hiraf.com, tipsumo.com, flypleasure.com and vancana.com.

It is common to find these name servers paired with the name servers verification-yhehuhyrvixzqbtydgzisf.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.