topekachamber.com - robtex.com

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

topekachamber.com

DNSSEC⚠️ Not signed
NSns1.simonserv.com.ns-not-in-service.com ⚠️ Not in zone NS records
NSns2.simonserv.com.ns-not-in-service.com ⚠️ Not in zone NS records

com

Same first word

Previous names

Next names

DNS History

2 records (2 active, 0 former)

NSns1.simonserv.com.ns-not-in-service.comns2.simonserv.com.ns-not-in-service.com
●NSns1.simonserv.com.ns-not-in-service.com2026-09-28 → 2026-11-13 · 2 obs
● 2026-09-28 07:28:10
● 2026-11-13 17:00:46
●NSns2.simonserv.com.ns-not-in-service.com2026-09-28 → 2026-11-13 · 2 obs
● 2026-09-28 07:28:10
● 2026-11-13 17:00:46

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comj.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net...-
topekachamber.comns1.simonserv.com.ns-not-in-service.com, ns2.simonserv.com.ns-not-in-service.com2 records

✅ Authoritative Response

Server:216.251.45.125

NS records: ns1.simonserv.com.ns-not-in-service.com, ns2.simonserv.com.ns-not-in-service.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 283ms | Queries: -

📄 Records

TypeCountSample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.simonserv.com.ns-not-in-service.com, ns2.simonserv.com.ns-not-in-service.com)

Analysis

Name Servers

topekachamber.com has two authoritative name servers — ns1.simonserv.com.ns-not-in-service.com and ns2.simonserv.com.ns-not-in-service.com.

topekachamber.com and mangrub.com are among domains that share the same name servers.

The name servers for topekachamber.com overlap at least in part with those of other domains, including tahlequahok.com and myreferralplace.com.

The name servers ns1.meganameservers.com, ns2.meganameservers.com and ns3.meganameservers.com are commonly seen alongside these name servers.