turo-bit.net - robtex.com
turo-bit.net
| 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 | ||||||
net
| 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=1778452956 | ||||||
Same first word
turo-bit.net |
Similar names
DNS History
16 records (2 active, 14 former)
○NSdns.turo-bit.net2026-05-02 → 2026-05-10 · 2 obs
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○ 2026-05-10 22:59:04
○NSns1.1domain.org2017-01-12 → 2017-01-12 · 4 obs
○ 2016-05-01 02:26:58
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○NSns1.domainreg.name2015-06-13 → 2016-05-01 · 4 obs
● 2015-06-13 02:22:30
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
●NSns1.dyna-ns.net2026-05-02 → 2026-05-10 · 3 obs
○ 2017-01-12 02:53:12
● 2026-05-02 06:40:16
● 2026-05-10 22:59:04
● 2026-05-02 06:40:16
● 2026-05-10 22:59:04
○NSns1.turo-bit.net2026-05-02 → 2026-05-10 · 2 obs
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○ 2026-05-10 22:59:04
○NSns2.1domain.org2017-01-12 → 2017-01-12 · 4 obs
○ 2016-05-01 02:26:58
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○NSns2.domainreg.name2015-06-13 → 2016-05-01 · 4 obs
● 2015-06-13 02:22:30
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
●NSns2.dyna-ns.net2026-05-02 → 2026-05-10 · 3 obs
○ 2017-01-12 02:53:12
● 2026-05-02 06:40:16
● 2026-05-10 22:59:04
● 2026-05-02 06:40:16
● 2026-05-10 22:59:04
○NSns2.turo-bit.net2026-05-02 → 2026-05-10 · 2 obs
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○ 2026-05-10 22:59:04
○NSns3.1domain.org2017-01-12 → 2017-01-12 · 4 obs
○ 2016-05-01 02:26:58
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○NSns3.domainreg.name2015-06-13 → 2016-05-01 · 4 obs
● 2015-06-13 02:22:30
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
○NSns4.1domain.org2017-01-12 → 2017-01-12 · 4 obs
○ 2016-05-01 02:26:58
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○NSns4.domainreg.name2015-06-13 → 2016-05-01 · 4 obs
● 2015-06-13 02:22:30
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
● 2016-05-01 02:26:58
○ 2017-01-12 02:53:12
○ 2026-05-10 22:59:04
○MXmx.turo-bit.net2026-05-02 → 2026-05-10 · 2 obs
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○ 2026-05-10 22:59:04
○A185.9.159.1112026-05-02 → 2026-05-10 · 2 obs
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
○ 2026-05-10 22:59:04
○A88.85.84.1322015-06-13 → 2017-01-12 · 4 obs
● 2015-06-13 02:22:30
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
● 2017-01-12 02:53:12
○ 2026-05-02 06:40:16
○ 2026-05-10 22:59:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| turo-bit.net | ns2.dyna-ns.net, ns1.dyna-ns.net | 4 records |
✅ Authoritative Response
Server:162.159.26.92
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for turo-bit.net (unsigned zone)
⏱️ Timing
Total: 3365ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns2.dyna-ns.net, ns2.dyna-ns.net, ns1.dyna-ns.net...)
Analysis
Name Servers
turo-bit.net is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.
turo-bit.net uses the same name server setup as other domains, for instance istanbulolsan.shop, gov-kma.help, dashcams.in, genxetia.cyou and downtowntailoring.com.
Host names with four IP numbers
ns1.dyna-ns.net points 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 points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5