binarymen.com - dns.ninja
binarymen.com
| DNSSEC | ⚠️ Not signed | ||||||
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.netnstld@verisign-grs.com serial=1787272839 | ||||||
Previously MX for
binarymen.com |
Similar names
Previous names
Next names
DNS History
10 records (0 active, 10 former)
○NSns1.runhosting.com2015-08-09 → 2017-02-18 · 4 obs
● 2015-08-09 02:27:24
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
○NSns1.tunerpage.net2019-02-04 → 2019-02-04 · 4 obs
○ 2017-02-18 16:35:08
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
○NSns2.runhosting.com2015-08-09 → 2017-02-18 · 4 obs
● 2015-08-09 02:27:24
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
○NSns2.tunerpage.net2019-02-04 → 2019-02-04 · 4 obs
○ 2017-02-18 16:35:08
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
○MXbinarymen.com2019-02-04 → 2019-02-04 · 4 obs
○ 2017-02-18 16:35:08
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
○MXmx.binarymen.com2015-08-09 → 2017-02-18 · 4 obs
● 2015-08-09 02:27:24
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
○A185.176.40.652017-02-18 → 2017-02-18 · 4 obs
○ 2016-03-03 12:08:56
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
● 2017-02-18 16:35:08
○ 2019-02-04 06:29:14
○ 2026-08-21 01:06:04
○A37.9.62.1302019-02-04 → 2019-02-04 · 4 obs
○ 2017-02-18 16:35:08
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
● 2019-02-04 06:29:14
○ 2026-08-19 20:05:22
○ 2026-08-21 01:06:04
○A82.197.130.1362015-11-27 → 2016-03-03 · 5 obs
○ 2015-08-09 02:27:24
● 2015-11-27 03:02:02
● 2016-03-03 12:08:56
○ 2017-02-18 16:35:08
○ 2026-08-21 01:06:04
● 2015-11-27 03:02:02
● 2016-03-03 12:08:56
○ 2017-02-18 16:35:08
○ 2026-08-21 01:06:04
○A83.125.80.2212015-08-09 → 2015-08-09 · 3 obs
● 2015-08-09 02:27:24
○ 2015-11-27 03:02:02
○ 2026-08-21 01:06:04
○ 2015-11-27 03:02:02
○ 2026-08-21 01:06:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
✅ Authoritative Response
Server:192.52.178.30
NS records: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1678ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|