binaryjs.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`binaryjs.com`

DNSSEC	⚠️ Not signed
A	5.133.197.12^{🇸🇪 INTERNETBOLAGET5.133.192.0/19}
NS	`ns1.nameserverseo.com` ⭐ ⚠️ Not in parent delegation
		A	207.91.192.132^{🇺🇸 AS54163207.91.192.0/24 123.Net, Inc.}
			PTR	`ns1.nameserverseo.com`
NS	`ns1.binaryjs.com` ⚠️ Not in zone NS records
NS	`ns2.binaryjs.com` ⚠️ Not in zone NS records
NS	`ns2.nameserverseo.com` ⚠️ Not in parent delegation
		A	170.187.160.207^{🇺🇸 AKAMAI-LINODE-AP170.187.160.0/21 Akamai Technologies}
			PTR	`ns2.nameserverseo.com`
NS	`ns3.nameserverseo.com` ⚠️ Not in parent delegation
		A	104.237.135.95^{🇺🇸 AKAMAI-LINODE-AP104.237.128.0/21 Akamai Technologies}
			PTR	`ns3.nameserverseo.com`
MX	`binaryjs.com` ⭐
		A	5.133.197.12^{🇸🇪 INTERNETBOLAGET5.133.192.0/19}
SOA	`ns1.nameserverseo.com`server@binaryjs.com 2026-08-19 #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=1787239704

WOT: SAFE (72/100)

MX for

binaryjs.com

Same first word

binaryjs.com

Previous names

Next names

DNS History

22 records (7 active, 15 former)

○NSdns1.name-services.com2016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

○NSdns2.name-services.com2016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

○NSdns3.name-services.com2016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

○NSdns4.name-services.com2016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

○NSdns5.name-services.com2016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

●NSns1.binaryjs.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○NSns1.dreamhost.com2015-07-23 → 2016-03-19 · 4 obs

● 2015-07-23 09:04:24
● 2016-03-19 05:15:18
○ 2016-07-22 14:06:10
○ 2026-08-20 15:53:18

●NSns1.nameserverseo.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○NSns1.parkingcrew.net2017-07-02 → 2017-07-02 · 4 obs

○ 2016-07-22 14:06:10
● 2017-07-02 07:43:26
○ 2026-08-20 06:06:46
○ 2026-08-20 15:53:18

●NSns2.binaryjs.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○NSns2.dreamhost.com2015-07-23 → 2016-03-19 · 4 obs

● 2015-07-23 09:04:24
● 2016-03-19 05:15:18
○ 2016-07-22 14:06:10
○ 2026-08-20 15:53:18

●NSns2.nameserverseo.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○NSns2.parkingcrew.net2017-07-02 → 2017-07-02 · 4 obs

○ 2016-07-22 14:06:10
● 2017-07-02 07:43:26
○ 2026-08-20 06:06:46
○ 2026-08-20 15:53:18

○NSns3.dreamhost.com2015-07-23 → 2016-03-19 · 4 obs

● 2015-07-23 09:04:24
● 2016-03-19 05:15:18
○ 2016-07-22 14:06:10
○ 2026-08-20 15:53:18

●NSns3.nameserverseo.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

●MXbinaryjs.com2026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○MXmail.h-email.net2017-07-02 → 2017-07-02 · 3 obs

● 2017-07-02 07:43:26
○ 2026-08-20 06:06:46
○ 2026-08-20 15:53:18

○A185.53.178.62017-07-02 → 2017-07-02 · 4 obs

○ 2016-07-22 14:06:10
● 2017-07-02 07:43:26
○ 2026-08-20 06:06:46
○ 2026-08-20 15:53:18

○A192.30.252.1532015-07-23 → 2016-03-19 · 4 obs

● 2015-07-23 09:04:24
● 2016-03-19 05:15:18
○ 2016-07-22 14:06:10
○ 2026-08-20 15:53:18

○A192.30.252.1542015-07-23 → 2016-03-19 · 4 obs

● 2015-07-23 09:04:24
● 2016-03-19 05:15:18
○ 2016-07-22 14:06:10
○ 2026-08-20 15:53:18

●A5.133.197.122026-08-20 → 2026-08-20 · 3 obs

○ 2017-07-02 07:43:26
● 2026-08-20 06:06:46
● 2026-08-20 15:53:18

○A98.124.243.432016-07-22 → 2016-07-22 · 4 obs

○ 2016-03-19 05:15:18
● 2016-07-22 14:06:10
○ 2017-07-02 07:43:26
○ 2026-08-20 15:53:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net...	-
binaryjs.com	ns1.binaryjs.com, ns2.binaryjs.com	2 records

✅ Authoritative Response

Server:5.133.197.12

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binaryjs.com (unsigned zone)

⏱️ Timing

Total: 1303ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`5.133.197.12`
NS	3	`ns2.nameserverseo.com, ns3.nameserverseo.com...`
MX	1	`binaryjs.com (pri: 0)`
SOA	1	`ns1.nameserverseo.com server.binaryjs.co`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.binaryjs.com, ns2.binaryjs.com)

Analysis

Mail Server Role

binaryjs.com acts as its own mail server.

IP Addresses

binaryjs.com points to a single IP number: 5.133.197.12.

Name Servers

Delegation for binaryjs.com is to five name servers: ns1.binaryjs.com, ns2.binaryjs.com, ns1.nameserverseo.com and two others.

The name servers of binaryjs.com overlap at least partially with those of other domains — among them starcky.com, lebanonembassy.net, dvm.nu and two more.

These name servers commonly appear in delegations together with ns2.nameserverseo.com, ns3.nameserverseo.com, ns1.coppelltxgaragedoor.com and 7 other.

The hostnames ns1.nameserverseo.com, ns2.nameserverseo.com and ns3.nameserverseo.com each resolve to a single IP: ns1.nameserverseo.com → 207.91.192.132, ns2.nameserverseo.com → 170.187.160.207, ns3.nameserverseo.com → 104.237.135.95.

Mail Servers

binaryjs.com has a single mail server: binaryjs.com itself.

binaryjs.com directs to just one IP number, 5.133.197.12.