34sec.com - dns.ninja
34sec.com
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=1782283340 | ||||||
Same first word
34sec.com |
Similar names
DNS History
7 records (6 active, 1 former)
○A69.64.147.2422015-07-14 → 2017-02-20 · 3 obs
● 2017-02-20 05:05:56
○ 2026-06-24 07:06:08
●A91.195.240.822026-06-24 → 2026-06-24 · 2 obs
● 2026-06-24 07:06:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, i.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net... | - |
| 34sec.com | ns1mpz.name.com, ns2bkr.name.com, ns3bgq.name.com, ns4lny.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1mpz.name.com, ns2bkr.name.com, ns3bgq.name.com, ns4lny.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 34sec.com (unsigned zone)
⏱️ Timing
Total: 143ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.82 |
| NS | 4 | ns1mpz.name.com, ns2bkr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1mpz.name.com, ns1mpz.name.com, ns2bkr.name.com...)
Analysis
IP Addresses
34sec.com points to a single IP number: 91.195.240.82.
Additional host names — stedi.biz, ero.eroreader.com, zandbak.info and two others — share IP numbers with 34sec.com.
Name Servers
Delegation for 34sec.com is to five name servers: ns1.name.com, ns1mpz.name.com, ns2bkr.name.com and two others.
At least some of 34sec.com's name servers are shared with other domains, for example 5p955.com, jg48fhd.com, dylan.biz and two more.
These name servers tend to co-occur with ns4lny.name.com, ns3bgq.name.com, ns1cnb.name.com and 7 other name servers in the same DNS delegations.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1mpz.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2bkr.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3bgq.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4lny.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1mpz.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1mpz.name.com resolve to 163.114.216.17 IP addresses each.