teckube.com - robtex.com
teckube.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=1784540177 | ||||||
MX for
teckube.com |
Same first word
teckube.com |
Similar names
DNS History
6 records (6 active, 0 former)
●MXteckube.com2026-07-16 → 2026-07-20 · 2 obs
● 2026-07-20 09:49:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| teckube.com | ns1bqx.name.com, ns2clp.name.com, ns3gxy.name.com, ns4fmw.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bqx.name.com, ns2clp.name.com, ns3gxy.name.com, ns4fmw.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for teckube.com (unsigned zone)
⏱️ Timing
Total: 135ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1bqx.name.com, ns2clp.name.com... |
| MX | 1 | teckube.com (pri: 10) |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1bqx.name.com, ns1bqx.name.com, ns2clp.name.com...)
Analysis
Mail Server Role
teckube.com handles its own mail, functioning as its own mail server.
Name Servers
teckube.com delegates to five name servers: ns1.name.com, ns1bqx.name.com, ns2clp.name.com and two others.
teckube.com has at least partial name server overlap with other domains, such as malamatrimonial.com, streetprophets.com, kenauer.com and two others.
ns4fmw.name.com, ns3gxy.name.com and ns1hwy.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names that have two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bqx.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2clp.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gxy.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fmw.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bqx.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bqx.name.com resolve to 163.114.216.17 IP addresses each.