`binaryprotocol.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	`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`
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`
TXT	`v=spf1 -all`
SOA	`ns2.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=1781000906

Same first word

binaryprotocol.com

DNS History

8 records (4 active, 4 former)

○NSns.123-reg.co.uk2015-06-13 → 2016-12-04 · 4 obs

● 2015-06-13 10:25:16
● 2016-12-04 00:15:56
○ 2026-03-05 13:01:18
○ 2026-06-09 10:31:38

●NSns1.afternic.com2026-03-05 → 2026-06-09 · 3 obs

○ 2016-12-04 00:15:56
● 2026-03-05 13:01:18
● 2026-06-09 10:31:38

○NSns2.123-reg.co.uk2015-06-13 → 2016-12-04 · 4 obs

● 2015-06-13 10:25:16
● 2016-12-04 00:15:56
○ 2026-03-05 13:01:18
○ 2026-06-09 10:31:38

●NSns2.afternic.com2026-03-05 → 2026-06-09 · 3 obs

○ 2016-12-04 00:15:56
● 2026-03-05 13:01:18
● 2026-06-09 10:31:38

○MX.2026-03-05 → 2026-06-09 · 2 obs

○ 2026-03-05 13:01:18
○ 2026-06-09 10:31:38

●A13.248.169.482026-03-05 → 2026-06-09 · 3 obs

○ 2016-12-04 00:15:56
● 2026-03-05 13:01:18
● 2026-06-09 10:31:38

●A76.223.54.1462026-03-05 → 2026-06-09 · 3 obs

○ 2016-12-04 00:15:56
● 2026-03-05 13:01:18
● 2026-06-09 10:31:38

○A94.136.40.822015-06-13 → 2016-12-04 · 4 obs

● 2015-06-13 10:25:16
● 2016-12-04 00:15:56
○ 2026-03-05 13:01:18
○ 2026-06-09 10:31:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
binaryprotocol.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:97.74.98.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binaryprotocol.com (unsigned zone)

⏱️ Timing

Total: 170ms | 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	`ns1.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

binaryprotocol.com points to two IP numbers: 13.248.169.48 and 76.223.54.146.

Two other host names, along with mail2.nordfusion.com, wildmountain.org and bos.3dl.us, also share IP numbers with binaryprotocol.com.

Name Servers

binaryprotocol.com is served by two delegated name servers, ns1.afternic.com and ns2.afternic.com.

binaryprotocol.com shares its NS records with other domains, for example mail.ifih.org, ratmir.com, foriner.com and two others.

The name servers of binaryprotocol.com overlap at least partially with those of other domains — among them cloudsec.uk, relysoft.com, sneeringly.com and two more.

These name servers commonly appear alongside the name servers verification-urj2ap2akmgcchkhharttb.ns101.verify.hn and verification-dpwdssre8nsafsansyvhjl.ns101.verify.hn.

Each of the two host names carries two IP addresses: ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45, and ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45.

binaryprotocol.com - robtex.com