binarymachine.net - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`binarymachine.net`

DNSSEC	⚠️ Not signed
A	142.56.232.246^{🇺🇸 ALLO142.56.224.0/19}
NS	`ns1.dnsimple-edge.com` ⭐
		A	2620:111:8004::53^{🇺🇸 AS327712620:111:8004::/48 DNSimple Corporation}
		A	199.247.152.53^{🇺🇸 AS32771199.247.152.0/24 DNSimple Corporation}
NS	`ns2.dnsimple-edge.net`
		A	2620:111:8005::53^{🇺🇸 AS327712620:111:8005::/48 Vultr Customer Route}
		A	199.247.153.53^{🇺🇸 AS32771199.247.153.0/24 Vultr Customer Route}
NS	`ns3.dnsimple-edge.io`
		A	2620:111:8006::53^{🇺🇸 AS327712620:111:8006::/48 DNSimple Corporation}
		A	199.247.154.53^{🇺🇸 AS32771199.247.154.0/24 DNSimple Corporation}
NS	`ns4.dnsimple-edge.org`
		A	2620:111:8007::53^{🇺🇸 AS327712620:111:8007::/48 Vultr Customer Route}
		A	199.247.155.53^{🇺🇸 AS32771199.247.155.0/24 Vultr Customer Route}
TXT	`protonmail-verification=7676f0b5a646b8de589134ab3358c98621f9f0e0`
SOA	`ns1.dnsimple-edge.com`admin@dnsimple.com serial=1465028574

`net`

	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=1787343189

Same first word

binarymachine.com

binarymachine.net

Previous names

Next names

DNS History

18 records (5 active, 13 former)

●NSns1.dnsimple-edge.com2026-08-21 → 2026-08-21 · 3 obs

○ 2017-02-18 17:06:58
● 2026-08-21 03:05:06
● 2026-08-21 20:30:04

○NSns1.dnsimple.com2017-02-18 → 2017-02-18 · 4 obs

○ 2016-07-09 05:37:12
● 2017-02-18 17:06:58
○ 2026-08-21 03:05:06
○ 2026-08-21 20:30:04

●NSns2.dnsimple-edge.net2026-08-21 → 2026-08-21 · 3 obs

○ 2017-02-18 17:06:58
● 2026-08-21 03:05:06
● 2026-08-21 20:30:04

○NSns2.dnsimple.com2017-02-18 → 2017-02-18 · 4 obs

○ 2016-07-09 05:37:12
● 2017-02-18 17:06:58
○ 2026-08-21 03:05:06
○ 2026-08-21 20:30:04

●NSns3.dnsimple-edge.io2026-08-21 → 2026-08-21 · 3 obs

○ 2017-02-18 17:06:58
● 2026-08-21 03:05:06
● 2026-08-21 20:30:04

○NSns3.dnsimple.com2017-02-18 → 2017-02-18 · 4 obs

○ 2016-07-09 05:37:12
● 2017-02-18 17:06:58
○ 2026-08-21 03:05:06
○ 2026-08-21 20:30:04

●NSns4.dnsimple-edge.org2026-08-21 → 2026-08-21 · 3 obs

○ 2017-02-18 17:06:58
● 2026-08-21 03:05:06
● 2026-08-21 20:30:04

○NSns4.dnsimple.com2017-02-18 → 2017-02-18 · 4 obs

○ 2016-07-09 05:37:12
● 2017-02-18 17:06:58
○ 2026-08-21 03:05:06
○ 2026-08-21 20:30:04

○NSns71.domaincontrol.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○NSns72.domaincontrol.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○MXalt1.aspmx.l.google.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○MXalt2.aspmx.l.google.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○MXaspmx.l.google.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○MXaspmx2.googlemail.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

○MXaspmx3.googlemail.com2015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

●A142.56.232.2462026-08-21 → 2026-08-21 · 3 obs

○ 2017-02-18 17:06:58
● 2026-08-21 03:05:06
● 2026-08-21 20:30:04

○A151.101.36.1332017-02-18 → 2017-02-18 · 4 obs

○ 2016-07-09 05:37:12
● 2017-02-18 17:06:58
○ 2026-08-21 03:05:06
○ 2026-08-21 20:30:04

○A184.168.221.372015-08-08 → 2016-03-07 · 4 obs

● 2015-08-08 19:57:16
● 2016-03-07 08:48:30
○ 2016-07-09 05:37:12
○ 2026-08-21 20:30:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
binarymachine.net	ns4.dnsimple-edge.org, ns2.dnsimple-edge.net, ns3.dnsimple-edge.io, ns1.dnsimple-edge.com	2 records

✅ Authoritative Response

Server:199.247.154.53

NS records: ns4.dnsimple-edge.org, ns2.dnsimple-edge.net, ns3.dnsimple-edge.io, ns1.dnsimple-edge.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarymachine.net (unsigned zone)

⏱️ Timing

Total: 419ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`142.56.232.246`
NS	4	`ns1.dnsimple-edge.com, ns2.dnsimple-edge.net...`
TXT	1	`protonmail-verification=7676f0b5a646b8de`
SOA	1	`ns1.dnsimple-edge.com admin.dnsimple.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2.dnsimple-edge.net, ns2.dnsimple-edge.net)

Analysis

IP Addresses

binarymachine.net resolves to just one IP address, 142.56.232.246.

Name Servers

The NS records for binarymachine.net point to four name servers: ns1.dnsimple-edge.com, ns3.dnsimple-edge.io, ns2.dnsimple-edge.net and ns4.dnsimple-edge.org.

binarymachine.net has at least partial name server overlap with other domains, such as bodil.org, ncilifeaid.com, codedangerously.com and two others.

It is common to see these name servers used together with name servers ns1.dnsimple.com and ns3.dnsimple.com.

ns1.dnsimple-edge.com, ns3.dnsimple-edge.io, ns2.dnsimple-edge.net and ns4.dnsimple-edge.org all point to exactly two IP numbers each: ns1.dnsimple-edge.com → 199.247.152.53 and 2620:111:8004::53; ns3.dnsimple-edge.io → 199.247.154.53 and 2620:111:8006::53; ns2.dnsimple-edge.net → 199.247.153.53 and 2620:111:8005::53; ns4.dnsimple-edge.org → 199.247.155.53 and 2620:111:8007::53.