`binarydistrict.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.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net serial=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

WOT: SAFE (50/100)

Same first word

binarydistrict.com

DNS History

8 records (4 active, 4 former)

●NSns1.afternic.com2026-02-17 → 2026-03-07 · 3 obs

○ 2017-07-02 23:32:44
● 2026-02-17 20:11:40
● 2026-03-07 13:18:14

○NSns1.reg.ru2017-07-02 → 2017-07-02 · 3 obs

● 2017-07-02 23:32:44
○ 2026-02-17 20:11:40
○ 2026-03-07 13:18:14

●NSns2.afternic.com2026-02-17 → 2026-03-07 · 3 obs

○ 2017-07-02 23:32:44
● 2026-02-17 20:11:40
● 2026-03-07 13:18:14

○NSns2.reg.ru2017-07-02 → 2017-07-02 · 3 obs

● 2017-07-02 23:32:44
○ 2026-02-17 20:11:40
○ 2026-03-07 13:18:14

○MX.2026-02-17 → 2026-03-07 · 2 obs

○ 2026-02-17 20:11:40
○ 2026-03-07 13:18:14

●A13.248.169.482026-02-17 → 2026-03-07 · 3 obs

○ 2017-07-02 23:32:44
● 2026-02-17 20:11:40
● 2026-03-07 13:18:14

○A194.58.112.1732017-07-02 → 2017-07-02 · 3 obs

● 2017-07-02 23:32:44
○ 2026-02-17 20:11:40
○ 2026-03-07 13:18:14

●A76.223.54.1462026-02-17 → 2026-03-07 · 3 obs

○ 2017-07-02 23:32:44
● 2026-02-17 20:11:40
● 2026-03-07 13:18:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
binarydistrict.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server: 173.201.66.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarydistrict.com (unsigned zone)

⏱️ Timing

Total: 99ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns2.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

binarydistrict.com points to two IPs: 13.248.169.48 and 76.223.54.146.

Other host names including placementpanda.com, think(0x65726f746963).com, twinphonic.com, surfchannels.com and blog.ms share IP numbers with binarydistrict.com.

Name Servers

binarydistrict.com's delegation uses two name servers, ns1.afternic.com and ns2.afternic.com.

binarydistrict.com shares the same name server setup as other domains, for example thenetjobs.com, eafl.org, jjas.org, friendlystraws.com and newspaper.tv.

binarydistrict.com at least partially shares name servers with other domains, including 5dfitness.com, idyg.com, ponomeru.com, invernessproperty.com and gde.me.

Host names with two IPs:

ns1.afternic.com points to: 2603:5:2126::45 and 97.74.98.69

ns2.afternic.com points to: 2603:5:2226::45 and 173.201.66.69

binarydistrict.com - robtex.com