tldnames.name - robtex.com
tldnames.name
| DNSSEC | ⚠️ Not signed | ||||||
| A | 185.65.56.178🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap | ||||||
| PTR | parking.namebay.com | ||||||
| NS | ns1.validname.com ⭐ | ||||||
| A | 2001:4ba0:cafe:532::1🇩🇪 MYLOC-AS2001:4ba0::/32 myLoc managed IT AG | ||||||
| PTR | dnssec1.namebay.com | ||||||
| A | 2a01:c8:ff00:201::133🇫🇷 NAMESHIELD2a01:c8:ff00::/40 Global IPv6 route to Namebay | ||||||
| A | 62.141.38.216🇩🇪 MYLOC-AS62.141.32.0/20 myLoc managed IT AG | ||||||
| PTR | smtp12.validname.com | ||||||
| A | 185.65.56.133🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap | ||||||
| PTR | dns1.namebay.com | ||||||
| NS | ns2.validname.com | ||||||
| A | 2001:41d0:203:ddee::34🇫🇷 OVH2001:41d0::/32 IPv6 | ||||||
| PTR | ns2.namebay.com | ||||||
| A | 2a01:c8:ff00:201::134🇫🇷 NAMESHIELD2a01:c8:ff00::/40 Global IPv6 route to Namebay | ||||||
| A | 91.134.185.34🇫🇷 OVH91.134.0.0/16 | ||||||
| PTR | dns4.namebay.com | ||||||
| A | 185.65.56.134🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap | ||||||
| PTR | dns2.namebay.com | ||||||
| SOA | ns1.validname.comadmin@validname.com 2017-06-03 #8 | ||||||
name
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ac1.nstld.com ⭐ | ||||||
| NS | ac2.nstld.com | ||||||
| NS | ac3.nstld.com | ||||||
| NS | ac4.nstld.com | ||||||
| SOA | ac1.nstld.cominfo@verisign-grs.com serial=1774830242 | ||||||
Same first word
Similar names
DNS History
3 records (3 active, 0 former)
●NSns1.validname.com2018-01-18 → 2026-03-30 · 2 obs
● 2026-03-30 00:52:04
●NSns2.validname.com2018-01-18 → 2026-03-30 · 2 obs
● 2026-03-30 00:52:04
●A185.65.56.1782018-01-18 → 2026-03-30 · 2 obs
● 2026-03-30 00:52:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| name | ac1.nstld.com, ac2.nstld.com, ac3.nstld.com, ac4.nstld.com | 8 records |
| tldnames.name | ns2.validname.com, ns1.validname.com | - |
✅ Authoritative Response
Server:91.134.185.34
NS records: ns2.validname.com, ns1.validname.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tldnames.name (unsigned zone)
⏱️ Timing
Total: 633ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.65.56.178 |
| NS | 2 | ns2.validname.com, ns1.validname.com |
| SOA | 1 | ns1.validname.com admin.validname.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ac1.nstld.com, ac2.nstld.com, ac3.nstld.com...)
Analysis
IP Addresses
tldnames.name resolves to one IP number: 185.65.56.178.
other host names including sbmnv.mobi, tapia.fr, axelis-ivry.com, ozeair.com and nomadkey.com share IP numbers with tldnames.name.
Name Servers
tldnames.name is delegated to two name servers ns1.validname.com and ns2.validname.com.
tldnames.name shares the same name server setup as other domains, for instance zemail.org, technichauffe.fr, alp-planning.com, immobilier-auvergne.net and alfocea.fr.
tldnames.name at least partially shares name servers with other domains, for instance locstudio.fr, deux-magots.eu, casinos-de-montecarlo.com and bs.digital.
These name servers are commonly used alongside dns1.namebay.com and dns2.namebay.com.
Host names with four IP numbers: ns1.validname.com points to 2001:4ba0:cafe:532::1, 2a01:c8:ff00:201::133, 62.141.38.216 and 185.65.56.133; ns2.validname.com points to 2001:41d0:203:ddee::34, 2a01:c8:ff00:201::134, 91.134.185.34 and 185.65.56.134.