servercode.top - dns.ninja
servercode.top
| DNSSEC | ⚠️ Not signed | ||||||
| NS | pns1.regery.net ⚠️ Not in zone NS records | ||||||
| A | 188.40.168.194🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1 | ||||||
| PTR | static.194.168.40.188.clients.your-server.de | ||||||
| NS | pns2.regery.net ⚠️ Not in zone NS records | ||||||
| A | 188.40.168.197🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1 | ||||||
| PTR | static.197.168.40.188.clients.your-server.de | ||||||
| NS | pns3.regery.net ⚠️ Not in zone NS records | ||||||
| A | 188.40.168.194🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1 | ||||||
| PTR | static.194.168.40.188.clients.your-server.de | ||||||
top
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.zdnscloud.com ⭐ | ||||||
| NS | a.zdnscloud.cn | ||||||
| NS | b.zdnscloud.cn | ||||||
| NS | c.zdnscloud.com | ||||||
| NS | d.zdnscloud.com | ||||||
| NS | e.zdnscloud.cn | ||||||
| NS | f.zdnscloud.cn | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2026-09-04_01:05:02 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1396961092 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
9 records (3 active, 6 former)
○NSaurora.ns.cloudflare.com2026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
○NSdimitris.ns.cloudflare.com2026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
●NSpns1.regery.net2026-09-03 → 2026-09-03 · 3 obs
● 2026-09-03 17:09:44
● 2026-09-03 17:09:46
●NSpns2.regery.net2026-09-03 → 2026-09-03 · 3 obs
● 2026-09-03 17:09:44
● 2026-09-03 17:09:46
●NSpns3.regery.net2026-09-03 → 2026-09-03 · 3 obs
● 2026-09-03 17:09:44
● 2026-09-03 17:09:46
○A104.21.31.2342026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
○A172.67.180.1912026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
○A2606:4700:3033::ac43:b4bf2026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
○A2606:4700:3035::6815:1fea2026-09-01 → 2026-09-01 · 3 obs
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com... | 9 records |
| servercode.top | pns1.regery.net, pns2.regery.net, pns3.regery.net | - |
✅ Authoritative Response
Server:188.40.168.194
NS records: pns1.regery.net, pns2.regery.net, pns3.regery.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for servercode.top (unsigned zone)
⏱️ Timing
Total: 1655ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 9
Out-of-bailiwick: 9 (a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com...)
Analysis
Name Servers
servercode.top has three name servers — pns1.regery.net, pns2.regery.net and pns3.regery.net.
servercode.top has at least partial name server overlap with other domains, such as specteh.org.ua, nusaspin.net, betshezi.net and two others.
pns1.regery.net, pns2.regery.net and pns3.regery.net each resolve to a single IP address: pns1.regery.net resolves to 188.40.168.194, pns2.regery.net resolves to 188.40.168.197 and pns3.regery.net resolves to 188.40.168.194.
The host names pns1.regery.net and pns3.regery.net both resolve to 188.40.168.194 IP addresses.