runnerchain.com - dns.ninja

runnerchain.com

DNSSEC⚠️ Not signed
A20.125.28.80🇺🇸 Microsoft20.64.0.0/10
NSns1.dnx.com ⭐ ⚠️ Not in zone NS records
A40.76.143.175🇺🇸 Microsoft40.76.0.0/14
NSns2.dnx.com ⚠️ Not in zone NS records
A50.85.209.175🇺🇸 Microsoft50.85.0.0/16
SOAns1.dnx.comhostmaster@dnx.com 2025-09-19 #1

com

Previously MX for

Same first word

Similar names

DNS History

12 records (3 active, 9 former)

2020202120222023202420252026NSns1.dnx.comns2.dnx.comns1.atom.comns1.dnsowl.comns2.atom.comns2.dnsowl.comns3.dnsowl.comns3.verification-nleonmcfkcimdoyulhuayj.ns101.verify.hnMXrunnerchain.comA20.125.28.80212.119.32.23052.20.84.62
NSns1.atom.com2026-03-19 → 2026-04-10 · 4 obs
○ 2019-12-15 09:09:42
● 2026-03-19 06:34:36
● 2026-04-10 21:35:34
○ 2026-07-04 11:42:48
NSns1.dnsowl.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 09:09:42
○ 2026-03-19 06:34:36
○ 2026-07-04 11:42:48
NSns1.dnx.com2026-07-04 → 2026-07-04 · 2 obs
○ 2026-04-10 21:35:34
● 2026-07-04 11:42:48
NSns2.atom.com2026-03-19 → 2026-04-10 · 4 obs
○ 2019-12-15 09:09:42
● 2026-03-19 06:34:36
● 2026-04-10 21:35:34
○ 2026-07-04 11:42:48
NSns2.dnsowl.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 09:09:42
○ 2026-03-19 06:34:36
○ 2026-07-04 11:42:48
NSns2.dnx.com2026-07-04 → 2026-07-04 · 2 obs
○ 2026-04-10 21:35:34
● 2026-07-04 11:42:48
NSns3.dnsowl.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 09:09:42
○ 2026-03-19 06:34:36
○ 2026-07-04 11:42:48
NSns3.verification-nleonmcfkcimdoyulhuayj.ns101.verify.hn2026-03-19 → 2026-04-10 · 4 obs
○ 2019-12-15 09:09:42
● 2026-03-19 06:34:36
● 2026-04-10 21:35:34
○ 2026-07-04 11:42:48
MXrunnerchain.com2019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 09:09:42
○ 2026-03-19 06:34:36
○ 2026-07-04 11:42:48
A20.125.28.802026-07-04 → 2026-07-04 · 2 obs
○ 2026-04-10 21:35:34
● 2026-07-04 11:42:48
A212.119.32.2302019-12-15 → 2019-12-15 · 3 obs
● 2019-12-15 09:09:42
○ 2026-03-19 06:34:36
○ 2026-07-04 11:42:48
A52.20.84.622026-03-19 → 2026-04-10 · 4 obs
○ 2019-12-15 09:09:42
● 2026-03-19 06:34:36
● 2026-04-10 21:35:34
○ 2026-07-04 11:42:48

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:50.85.209.175

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for runnerchain.com (unsigned zone)

⏱️ Timing

Total: 407ms | Queries: -

📄 Records

TypeCountSample Data
A120.125.28.80
SOA1ns1.dnx.com hostmaster.dnx.com

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

runnerchain.com has exactly one IP address — 20.125.28.80.

jcn.ca, radiationlawsuit.com, ameen.com plus two other host names have IP numbers in common with runnerchain.com.

Name Servers

runnerchain.com is delegated to two name servers: ns1.dnx.com and ns2.dnx.com.

The name server configuration of runnerchain.com is shared with other domains, for instance dronetech.ca, betty.im, environav.com and two others.

There is at least partial name server overlap between runnerchain.com and other domains — www.angles.com, www.superbattorneys.com, mx.mx.mx.neondex.com and two more among them.

These name servers regularly appear alongside verification-ivgrjvjkrzbgkhmtmq2uzh.ns101.verify.hn, ns1.atom.com, ns2.atom.com and 6 other name servers in NS record sets.

ns1.dnx.com40.76.143.175 and ns2.dnx.com50.85.209.175: one IP number per host name.