binarymagnet.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`binarymagnet.com`

DNSSEC	⚠️ Not signed
A	216.40.34.41^{🇨🇦 TUCOWS216.40.34.0/24}
NS	`ns1.hover.com` ⭐
		A	2604:4000:0:d:216:40:47:26^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.hover.com`
		A	216.40.47.26^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.hover.com`
NS	`ns2.hover.com`
		A	2604:4000:2800:d:64:99:148:13^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.hover.com`
		A	64.98.148.13^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.hover.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c29::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f27.1e100.net`
		A	172.253.62.26^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽²⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx4.googlemail.com`⁽³⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`aspmx5.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`keybase-site-verification=91Zhiea1E0SQMtWPTPId_5DcGnomfb1CXTAFt8Qykmc`
TXT	`google-site-verification=5Ycy4MD9D-qM6fQ2-Rdd3EjK1BfwgfaBJvzdGGZr3_Q`
SOA	`ns1.hover.com`dnsmaster@hover.com serial=1763519014

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

Same first word

binarymagnet.com

Previous names

Next names

DNS History

12 records (10 active, 2 former)

●NSns1.hover.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●NSns2.hover.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXalt1.aspmx.l.google.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXalt2.aspmx.l.google.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXaspmx.l.google.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXaspmx2.googlemail.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXaspmx3.googlemail.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXaspmx4.googlemail.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●MXaspmx5.googlemail.com2015-05-19 → 2026-08-19 · 2 obs

● 2015-05-19 07:43:24
● 2026-08-19 11:10:52

●A216.40.34.412026-08-18 → 2026-08-19 · 3 obs

○ 2017-05-13 10:58:38
● 2026-08-18 13:01:40
● 2026-08-19 11:10:52

○A64.98.145.302016-09-26 → 2017-05-13 · 5 obs

○ 2016-03-23 04:29:40
● 2016-09-26 01:22:48
● 2017-05-13 10:58:38
○ 2026-08-18 13:01:40
○ 2026-08-19 11:10:52

○A64.99.80.302015-05-19 → 2016-03-23 · 4 obs

● 2015-05-19 07:43:24
● 2016-03-23 04:29:40
○ 2016-09-26 01:22:48
○ 2026-08-19 11:10:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net...	-
binarymagnet.com	ns1.hover.com, ns2.hover.com	4 records

✅ Authoritative Response

Server:216.40.47.26

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarymagnet.com (unsigned zone)

⏱️ Timing

Total: 244ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.40.34.41`
NS	2	`ns2.hover.com, ns1.hover.com`
MX	7	`aspmx5.googlemail.com (pri: 30), alt1.aspmx.l.google.com (pri: 20)...`
TXT	2	`google-site-verification=5Ycy4MD9D-qM6fQ, keybase-site-verification=91Zhiea1E0SQMt`
SOA	1	`ns1.hover.com dnsmaster.hover.com`

📌 Glue Records Collected

Total: 4

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

Analysis

IP Addresses

binarymagnet.com directs to one IP number, which is 216.40.34.41.

Among the host names that share IP numbers with binarymagnet.com are askrespond.com, kinach.net, tfai.us and two others.

Name Servers

binarymagnet.com is served by two delegated name servers, ns1.hover.com and ns2.hover.com.

binarymagnet.com has the same name server delegation as a number of other domains, such as myrooms.co.uk, sigint.dev, lastlook.net and two more.

binarymagnet.com shares at least some of its name servers with other domains, for example distant-pla.net, topplays.com, anicast.es and economicalinsurance.biz.

Each of the two host names carries two IP addresses: ns1.hover.com points to 216.40.47.26 and 2604:4000:0:d:216:40:47:26, and ns2.hover.com points to 64.98.148.13 and 2604:4000:2800:d:64:99:148:13.

Mail Servers

binarymagnet.com uses 7 mail servers for delivery: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.

binarymagnet.com shares at least some of its mail servers with other domains — for example endodequebec.com, ladifference.com.mx, gruppofomat.com and two more.

It is common to find these mail servers paired with mail servers aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com and 3 more.

Hosts with two IP numbers each:

aspmx2.googlemail.com maps to two IP addresses — 192.178.234.26 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx4.googlemail.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1b.

aspmx5.googlemail.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1b.

aspmx.l.google.com maps to two IP addresses — 172.253.62.26 and 2607:f8b0:4004:c29::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.