sectaur.com - robtex.com
sectaur.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=1792822031 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-09-03 → 2026-10-24 · 2 obs
● 2026-10-24 06:57: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... | - |
| sectaur.com | ns1hwy.name.com, ns2dqx.name.com, ns3fgh.name.com, ns4fqz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1hwy.name.com, ns2dqx.name.com, ns3fgh.name.com, ns4fqz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sectaur.com (unsigned zone)
⏱️ Timing
Total: 181ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1hwy.name.com, ns2dqx.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1hwy.name.com, ns1hwy.name.com, ns2dqx.name.com...)
Analysis
IP Addresses
sectaur.com resolves to one IP address: 91.195.240.94.
qarar.app, ns1.korek.tel, glenbonilla.com and two other host names share IP numbers with sectaur.com.
Name Servers
sectaur.com has five name servers, which are ns1.name.com, ns1hwy.name.com, ns2dqx.name.com and two others.
sectaur.com has at least partial name server overlap with other domains, such as uccx.com, foxandbond.com, livewireairlines.net and two others.
ns4jnz.name.com, ns2fln.name.com and ns3fqs.name.com — plus 7 other name servers — are commonly paired with these name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dqx.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fgh.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fqz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1hwy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1hwy.name.com resolve to 163.114.216.17 IP addresses each.