servercode.top - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status

servercode.top

DNSSEC⚠️ Not signed
NSpns1.regery.net ⚠️ Not in zone NS records
A188.40.168.194🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1
PTRstatic.194.168.40.188.clients.your-server.de
NSpns2.regery.net ⚠️ Not in zone NS records
A188.40.168.197🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1
PTRstatic.197.168.40.188.clients.your-server.de
NSpns3.regery.net ⚠️ Not in zone NS records
A188.40.168.194🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1
PTRstatic.194.168.40.188.clients.your-server.de

top

DNSSEC🔒 Signed (DS record present)
NSa.zdnscloud.com
NSa.zdnscloud.cn
NSb.zdnscloud.cn
NSc.zdnscloud.com
NSd.zdnscloud.com
NSe.zdnscloud.cn
NSf.zdnscloud.cn
NSi.zdnscloud.cn
NSj.zdnscloud.com
TXT2026-09-04_01:05:02
SOAa.zdnscloud.comtd_dns_gtld@knet.cn serial=1396961092
⚠️ On DNS blocklist: spam-tlds

Same first word

Similar names

Previous names

Next names

DNS History

9 records (3 active, 6 former)

NSpns1.regery.netpns2.regery.netpns3.regery.netaurora.ns.cloudflare.comdimitris.ns.cloudflare.comA104.21.31.234172.67.180.1912606:4700:3033::ac43:b4bf2606:4700:3035::6815:1fea
NSaurora.ns.cloudflare.com2026-09-01 → 2026-09-01 · 3 obs
● 2026-09-01 10:13:58
○ 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-01 10:13:58
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46
NSpns1.regery.net2026-09-03 → 2026-09-03 · 3 obs
○ 2026-09-01 10:13:58
● 2026-09-03 17:09:44
● 2026-09-03 17:09:46
NSpns2.regery.net2026-09-03 → 2026-09-03 · 3 obs
○ 2026-09-01 10:13:58
● 2026-09-03 17:09:44
● 2026-09-03 17:09:46
NSpns3.regery.net2026-09-03 → 2026-09-03 · 3 obs
○ 2026-09-01 10:13:58
● 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-01 10:13:58
○ 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-01 10:13:58
○ 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-01 10:13:58
○ 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-01 10:13:58
○ 2026-09-03 17:09:44
○ 2026-09-03 17:09:46

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
topa.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com...9 records
servercode.toppns1.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

TypeCountSample 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.