latencybase.com - robtex.com
latencybase.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1a5c🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b9e🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.92Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| A | 162.159.27.158Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| NS | ns2.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1805🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1905🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.24.5Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
| A | 162.159.25.5Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
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=1771291435 | ||||||
PTR for
Subdomains
mx.latencybase.com |
Same first word
latencybase.com |
DNS History
7 records (2 active, 5 former)
○NSdns.latencybase.com2026-02-17 → 2026-02-17 · 3 obs
○ 2026-02-24 06:52:58
○ 2026-03-09 19:26:36
●NSns1.dyna-ns.net2026-02-24 → 2026-03-09 · 3 obs
● 2026-02-24 06:52:58
● 2026-03-09 19:26:36
○NSns1.latencybase.com2026-02-17 → 2026-02-17 · 3 obs
○ 2026-02-24 06:52:58
○ 2026-03-09 19:26:36
●NSns2.dyna-ns.net2026-02-24 → 2026-03-09 · 3 obs
● 2026-02-24 06:52:58
● 2026-03-09 19:26:36
○NSns2.latencybase.com2026-02-17 → 2026-02-17 · 3 obs
○ 2026-02-24 06:52:58
○ 2026-03-09 19:26:36
○MXmx.latencybase.com2026-02-17 → 2026-02-17 · 3 obs
○ 2026-02-24 06:52:58
○ 2026-03-09 19:26:36
○A184.154.126.62026-02-17 → 2026-02-17 · 3 obs
○ 2026-02-24 06:52:58
○ 2026-03-09 19:26:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, e.gtld-servers.net, k.gtld-servers.net, g.gtld-servers.net... | - |
| latencybase.com | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server: 162.159.27.158
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for latencybase.com (unsigned zone)
⏱️ Timing
Total: 321ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Hierarchy
latencybase.com is the parent of mx.latencybase.com.
Name Servers
latencybase.com is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.
latencybase.com shares the same name server setup as other domains, for example bumsfilme.net, g-mal.com, xnzz.net, 3650708.com and finchamlondon.com.
Host names with four IP numbers:
ns1.dyna-ns.net resolves to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158.
ns2.dyna-ns.net resolves to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.