binarynerd.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status

binarynerd.com

DNSSEC⚠️ Not signed
A13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix
PTRec2-13-56-33-8.us-west-1.compute.amazonaws.com
NSns1.brandbucket.com
A2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS
A54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix
PTRec2-54-241-53-41.us-west-1.compute.amazonaws.com
NSns2.brandbucket.com
A2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS
A18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix
PTRec2-18-221-52-246.us-east-2.compute.amazonaws.com
TXT27aab5373841b85aab94982ee19ab62f96481ed6
TXTafternic-verification-cvgUQU8SkLxsjXcPBSk2CM
TXTv=spf1 -all
TXTe698482e-dc42-43b0-81b6-91255326632c
SOAns1.brandbucket.commail@binarynerd.com 2024-03-05 #2

com

Same first word

Similar names

Previous names

Next names

DNS History

8 records (3 active, 5 former)

20162017201820192020202120222023202420252026NSns1.brandbucket.comns2.brandbucket.comns1.fatcow.comns2.fatcow.comMXmx.binarynerd.comA13.56.33.865.254.227.22465.254.248.203
NSns1.brandbucket.com2026-08-18 → 2026-08-22 · 3 obs
○ 2018-08-03 06:19:36
● 2026-08-18 16:02:46
● 2026-08-22 18:22:16
NSns1.fatcow.com2015-07-02 → 2018-08-03 · 4 obs
● 2015-07-02 09:15:44
● 2018-08-03 06:19:36
○ 2026-08-18 16:02:46
○ 2026-08-22 18:22:16
NSns2.brandbucket.com2026-08-18 → 2026-08-22 · 3 obs
○ 2018-08-03 06:19:36
● 2026-08-18 16:02:46
● 2026-08-22 18:22:16
NSns2.fatcow.com2015-07-02 → 2018-08-03 · 4 obs
● 2015-07-02 09:15:44
● 2018-08-03 06:19:36
○ 2026-08-18 16:02:46
○ 2026-08-22 18:22:16
MXmx.binarynerd.com2015-07-02 → 2018-08-03 · 4 obs
● 2015-07-02 09:15:44
● 2018-08-03 06:19:36
○ 2026-08-18 16:02:46
○ 2026-08-22 18:22:16
A13.56.33.82026-08-18 → 2026-08-22 · 3 obs
○ 2018-08-03 06:19:36
● 2026-08-18 16:02:46
● 2026-08-22 18:22:16
A65.254.227.2242016-06-19 → 2018-08-03 · 5 obs
○ 2016-02-22 14:42:08
● 2016-06-19 19:14:54
● 2018-08-03 06:19:36
○ 2026-08-18 16:02:46
○ 2026-08-22 18:22:16
A65.254.248.2032015-07-02 → 2016-02-22 · 4 obs
● 2015-07-02 09:15:44
● 2016-02-22 14:42:08
○ 2016-06-19 19:14:54
○ 2026-08-22 18:22:16

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
binarynerd.comns1.brandbucket.com, ns2.brandbucket.com2 records

✅ Authoritative Response

Server:54.241.53.41

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for binarynerd.com (unsigned zone)

⏱️ Timing

Total: 376ms | Queries: -

📄 Records

TypeCountSample Data
A113.56.33.8
NS2ns1.brandbucket.com, ns2.brandbucket.com
TXT427aab5373841b85aab94982ee19ab62f96481ed6, afternic-verification-cvgUQU8SkLxsjXcPBS...
SOA1ns1.brandbucket.com mail.binarynerd.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)

Analysis

IP Addresses

binarynerd.com has exactly one IP address — 13.56.33.8.

deliverybullet.com, therawarm.com, pendina.com plus two other host names have IP numbers in common with binarynerd.com.

Name Servers

binarynerd.com is delegated to two name servers: ns1.brandbucket.com and ns2.brandbucket.com.

The name server configuration of binarynerd.com is shared with other domains, for instance nggts.com, coldmocha.com, knotcloud.com and two others.

binarynerd.com partially shares its name servers with domains like statmotion.com and undumb.com.

ns1.brandbucket.com and ns2.brandbucket.com each resolve to two IP addresses: ns1.brandbucket.com points to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361, while ns2.brandbucket.com points to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8.