rosesbadcat.com - robtex.com
rosesbadcat.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=1776113752 | ||||||
Same first word
rosesbadcat.com |
Similar names
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| rosesbadcat.com | ns1dhq.name.com, ns2fln.name.com, ns3jkl.name.com, ns4cpw.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1dhq.name.com, ns2fln.name.com, ns3jkl.name.com, ns4cpw.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rosesbadcat.com (unsigned zone)
⏱️ Timing
Total: 139ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1dhq.name.com, ns2fln.name.com... |
| TXT | 1 | v=spf1 include:spf11.dailydeals.my inclu |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1dhq.name.com, ns1dhq.name.com, ns2fln.name.com...)
Analysis
Name Servers
rosesbadcat.com is delegated to five name servers: ns1.name.com, ns1dhq.name.com, ns2fln.name.com, ns3jkl.name.com and ns4cpw.name.com.
rosesbadcat.com at least partially shares name servers with other domains, including teiel.com, zaheer.me, tibou.com, novodora.com and ciumbek.com.
These name servers are commonly used with ns1cny.name.com, ns4hny.name.com, ns2ckr.name.com, ns1cnb.name.com, ns3cna.name.com, ns3dty.name.com, ns1dhl.name.com, ns1kwy.name.com, ns4lpv.name.com and ns2jqz.name.com.
Names with two IPs:
ns1.name.com points to 2a00:edc0:107::1 and 163.114.216.17.
ns1dhq.name.com points to 2a00:edc0:107::1 and 163.114.216.17.
ns2fln.name.com points to 2402:cf80:107::1 and 163.114.216.49.
ns3jkl.name.com points to 2a00:edc0:107::49 and 163.114.217.17.
ns4cpw.name.com points to 2402:cf80:107::49 and 163.114.217.49.
Names pointing to 2a00:edc0:107::1: ns1.name.com and ns1dhq.name.com.
Names pointing to 163.114.216.17: ns1.name.com and ns1dhq.name.com.
Note: 2a00:edc0:107::1 and 163.114.216.17 are targets for both ns1.name.com and ns1dhq.name.com.