binarysolo.com - dns.ninja

binarysolo.com

com

WOT: SAFE (74/100)

Previously MX for

Subdomains

Same first word

Similar names

DNS History

9 records (3 active, 6 former)

200920112013201520172019202120232025NSdns1.registrar-servers.comdns2.registrar-servers.comns1.bluehost.comns1.indievangamejam.tvns2.bluehost.comns2.indievangamejam.tvMXaspmx.l.google.combinarysolo.comA198.57.175.202
●NSdns1.registrar-servers.com2026-03-23 β†’ 2026-07-04 Β· 3 obs
β—‹ 2018-08-12 06:07:12
● 2026-03-23 23:00:28
● 2026-07-04 21:41:16
●NSdns2.registrar-servers.com2026-03-23 β†’ 2026-07-04 Β· 3 obs
β—‹ 2018-08-12 06:07:12
● 2026-03-23 23:00:28
● 2026-07-04 21:41:16
β—‹NSns1.bluehost.com2008-03-09 β†’ 2008-03-09 Β· 3 obs
● 2008-03-09 01:17:06
β—‹ 2015-06-21 06:27:24
β—‹ 2026-07-04 21:41:16
β—‹NSns1.indievangamejam.tv2015-06-21 β†’ 2018-08-12 Β· 5 obs
β—‹ 2008-03-09 01:17:06
● 2015-06-21 06:27:24
● 2018-08-12 06:07:12
β—‹ 2026-03-23 23:00:28
β—‹ 2026-07-04 21:41:16
β—‹NSns2.bluehost.com2008-03-09 β†’ 2008-03-09 Β· 3 obs
● 2008-03-09 01:17:06
β—‹ 2015-06-21 06:27:24
β—‹ 2026-07-04 21:41:16
β—‹NSns2.indievangamejam.tv2015-06-21 β†’ 2018-08-12 Β· 5 obs
β—‹ 2008-03-09 01:17:06
● 2015-06-21 06:27:24
● 2018-08-12 06:07:12
β—‹ 2026-03-23 23:00:28
β—‹ 2026-07-04 21:41:16
●MXaspmx.l.google.com2026-03-23 β†’ 2026-07-04 Β· 3 obs
β—‹ 2018-08-12 06:07:12
● 2026-03-23 23:00:28
● 2026-07-04 21:41:16
β—‹MXbinarysolo.com2008-03-09 β†’ 2018-08-12 Β· 4 obs
● 2008-03-09 01:17:06
● 2018-08-12 06:07:12
β—‹ 2026-03-23 23:00:28
β—‹ 2026-07-04 21:41:16
β—‹A198.57.175.2022015-06-21 β†’ 2018-08-12 Β· 5 obs
β—‹ 2008-03-09 01:17:06
● 2015-06-21 06:27:24
● 2018-08-12 06:07:12
β—‹ 2026-03-23 23:00:28
β—‹ 2026-07-04 21:41:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comm.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net...-
binarysolo.comdns1.registrar-servers.com, dns2.registrar-servers.com4 records

βœ… Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarysolo.com (unsigned zone)

⏱️ Timing

Total: 191ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS2dns1.registrar-servers.com, dns2.registrar-servers.com
MX1aspmx.l.google.com (pri: 1)
TXT1v=spf1 a mx include:_spf.mlsend.com incl
SOA1dns1.registrar-servers.com hostmaster.re

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

Hierarchy

binarysolo.com serves as the parent of 220-server.binarysolo.com.

Name Servers

Two name servers handle the delegation for binarysolo.com: dns1.registrar-servers.com and dns2.registrar-servers.com.

binarysolo.com has the same name server delegation as a number of other domains, such as soldmangachs.xyz, jobresumesite.com, sucastainability.com and two more.

binarysolo.com has at least partial name server overlap with other domains, such as kevinchabreck.com, alucency.com, atexcursions.com and two others.

These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

binarysolo.com routes its mail through a single mail server, aspmx.l.google.com.

binarysolo.com has the same mail server arrangement as a number of other domains, for example tlnx.net, ls-a-213.skima.is, sourceoneholdings.com and two more.

binarysolo.com shares at least some of its mail servers with other domains β€” for example risezusa.com, megatrade.lutsk.ua, ghcip.com and two more.

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

aspmx.l.google.com has two IP addresses: 142.251.167.27 and 2607:f8b0:4004:c07::1b.