🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`binarymastermind.com`

DNSSEC	⚠️ Not signed
A	160.124.12.246^{🇿🇦 POWERLINE-HK160.124.0.0/19 Proxy-registered route object}
NS	`ns1.dns.com` ⭐
		A	2001:df2:f080:2::1:1^{🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	154.86.21.128^{🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	177.2.31.128^{🇧🇷 AS-V177.2.0.0/18}
NS	`ns2.dns.com`
		A	2001:df2:f080:2::1:2^{🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	154.23.191.129^{🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	177.2.31.129^{🇧🇷 AS-V177.2.0.0/18}
SOA	`ns1.dns.com`admin@dns.com serial=1787073016

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

Same first word

binarymastermind.com

Previous names

Next names

DNS History

21 records (3 active, 18 former)

○NSkate.ns.cloudflare.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○NSned.ns.cloudflare.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

●NSns1.dns.com2026-08-28 → 2026-08-31 · 3 obs

○ 2017-02-04 16:13:48
● 2026-08-28 17:14:06
● 2026-08-31 21:06:42

●NSns2.dns.com2026-08-28 → 2026-08-31 · 3 obs

○ 2017-02-04 16:13:48
● 2026-08-28 17:14:06
● 2026-08-31 21:06:42

○NSns37.domaincontrol.com2016-05-03 → 2016-05-03 · 4 obs

○ 2016-01-29 06:41:28
● 2016-05-03 03:01:04
○ 2017-02-04 16:13:48
○ 2026-08-31 21:06:42

○NSns38.domaincontrol.com2016-05-03 → 2016-05-03 · 4 obs

○ 2016-01-29 06:41:28
● 2016-05-03 03:01:04
○ 2017-02-04 16:13:48
○ 2026-08-31 21:06:42

○NSns69.domaincontrol.com2015-06-23 → 2015-11-12 · 4 obs

● 2015-06-23 14:52:20
● 2015-11-12 23:31:02
○ 2016-01-29 06:41:28
○ 2026-08-31 21:06:42

○NSns70.domaincontrol.com2015-06-23 → 2015-11-12 · 4 obs

● 2015-06-23 14:52:20
● 2015-11-12 23:31:02
○ 2016-01-29 06:41:28
○ 2026-08-31 21:06:42

○MXalt1.aspmx.l.google.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○MXalt2.aspmx.l.google.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○MXaspmx.l.google.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○MXaspmx2.googlemail.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○MXaspmx3.googlemail.com2017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○MXmailstore1.secureserver.net2015-06-23 → 2015-11-12 · 4 obs

● 2015-06-23 14:52:20
● 2015-11-12 23:31:02
○ 2016-01-29 06:41:28
○ 2026-08-31 21:06:42

○MXsmtp.secureserver.net2015-06-23 → 2015-11-12 · 4 obs

● 2015-06-23 14:52:20
● 2015-11-12 23:31:02
○ 2016-01-29 06:41:28
○ 2026-08-31 21:06:42

○MXtmp2016-05-03 → 2016-05-03 · 4 obs

○ 2016-01-29 06:41:28
● 2016-05-03 03:01:04
○ 2017-02-04 16:13:48
○ 2026-08-31 21:06:42

○A107.154.106.422016-05-03 → 2016-05-03 · 4 obs

○ 2016-01-29 06:41:28
● 2016-05-03 03:01:04
○ 2017-02-04 16:13:48
○ 2026-08-31 21:06:42

○A107.154.109.422016-05-03 → 2016-05-03 · 4 obs

○ 2016-01-29 06:41:28
● 2016-05-03 03:01:04
○ 2017-02-04 16:13:48
○ 2026-08-31 21:06:42

●A160.124.12.2462026-08-28 → 2026-08-31 · 5 obs

○ 2017-02-04 16:13:48
● 2026-08-28 17:14:06
○ 2026-08-29 13:32:40
● 2026-08-29 17:00:04
● 2026-08-31 21:06:42

○A185.127.16.392017-02-04 → 2017-02-04 · 4 obs

○ 2016-05-03 03:01:04
● 2017-02-04 16:13:48
○ 2026-08-28 17:14:06
○ 2026-08-31 21:06:42

○A50.63.202.392015-06-23 → 2015-11-12 · 4 obs

● 2015-06-23 14:52:20
● 2015-11-12 23:31:02
○ 2016-01-29 06:41:28
○ 2026-08-31 21:06:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
binarymastermind.com	ns1.dns.com, ns2.dns.com	6 records

✅ Authoritative Response

Server:154.23.191.129

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarymastermind.com (unsigned zone)

⏱️ Timing

Total: 609ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`160.124.12.246`
NS	2	`ns1.dns.com, ns2.dns.com`
SOA	1	`ns1.dns.com admin.dns.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.dns.com, ns1.dns.com, ns1.dns.com...)

Analysis

IP Addresses

binarymastermind.com resolves to one IP address: 160.124.12.246.

Additional host names such as healthtripper.com, usadiscoverer.com, soft288.com and trifitfix.com share IP numbers with binarymastermind.com.

Name Servers

binarymastermind.com is served by two delegated name servers, ns1.dns.com and ns2.dns.com.

binarymastermind.com uses the same name servers as several other domains — among them 001game2.com, 00668449.com, 9x6v29.info and two more.

ns1.dns.com and ns2.dns.com each resolve to three IP addresses. ns1.dns.com resolves to 154.86.21.128, 177.2.31.128 and 2001:df2:f080:2::1:1. ns2.dns.com resolves to 154.23.191.129, 177.2.31.129 and 2001:df2:f080:2::1:2.

binarymastermind.com - robtex.com