2s2f.com - robtex.com
2s2f.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=1785850324 | ||||||
Same first word
Similar names
2f2s.com |
22fs.com |
f2s2.xyz |
sf22.ru |
fs22.net |
22sf.info |
sf22.cn |
s2f2.org |
fs22.lol |
22fs.de |
f22s.com |
sf22.org |
22sf.com |
f2s2.org |
fs22.com |
DNS History
5 records (4 active, 1 former)
○A69.64.147.2422015-07-19 → 2017-05-21 · 4 obs
● 2017-05-21 02:07:52
○ 2026-06-22 03:09:56
○ 2026-08-04 13:40:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| 2s2f.com | ns1dhl.name.com, ns2knz.name.com, ns3hjx.name.com, ns4fpy.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1dhl.name.com, ns2knz.name.com, ns3hjx.name.com, ns4fpy.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 2s2f.com (unsigned zone)
⏱️ Timing
Total: 204ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1dhl.name.com, ns1dhl.name.com, ns2knz.name.com...)
Analysis
Name Servers
The domain 2s2f.com is delegated to these four name servers: ns1dhl.name.com, ns2knz.name.com, ns3hjx.name.com and ns4fpy.name.com.
At least some of 2s2f.com's name servers are shared with other domains, for example hengbotong.com, thecarnegieproject.com, thevarols.com and two more.
These name servers tend to co-occur with ns1.name.com, ns1kpv.name.com, ns4lrt.name.com and 7 other name servers in the same DNS delegations.
Four hostnames, each resolving to a pair of IP addresses: ns1dhl.name.com directs to 163.114.216.17 and 2a00:edc0:107::1; ns2knz.name.com directs to 163.114.216.49 and 2402:cf80:107::1; ns3hjx.name.com directs to 163.114.217.17 and 2a00:edc0:107::49; ns4fpy.name.com directs to 163.114.217.49 and 2402:cf80:107::49.