nevadaforum.com - robtex.com

nevadaforum.com

DNSSEC⚠️ Not signed
NSdns1.registrar-servers.com ⭐
A2610:a1:1024::200🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
A156.154.132.200🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
NSdns2.registrar-servers.com
A2610:a1:1025::200🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
A156.154.133.200🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
SOAdns1.registrar-servers.comhostmaster@registrar-servers.com serial=1774349938

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1778408306

Same first word

nevadaforum.com

DNS History

19 records (2 active, 17 former)

200920112013201520172019202120232025NSdns1.registrar-servers.comdns2.registrar-servers.combuy.internettraffic.comns1.dsredirection.comns1.dynadot.comns1637.ztomy.comns2.dsredirection.comns2.dynadot.comns2637.ztomy.comsell.internettraffic.comA204.11.56.37208.73.212.1234.202.122.7735.169.225.24852.0.7.3069.172.201.15369.172.201.208CNAME77980.bodis.comPTRns1637.ztomy.com
○NSbuy.internettraffic.com2015-10-16 → 2016-04-26 · 5 obs
○ 2008-03-20 11:27:40
● 2015-10-16 21:46:36
● 2016-04-26 02:34:20
○ 2017-03-13 17:18:10
○ 2026-05-10 10:26:02
●NSdns1.registrar-servers.com2026-03-28 → 2026-05-10 · 3 obs
○ 2020-01-15 08:00:52
● 2026-03-28 14:22:06
● 2026-05-10 10:26:02
●NSdns2.registrar-servers.com2026-03-28 → 2026-05-10 · 3 obs
○ 2020-01-15 08:00:52
● 2026-03-28 14:22:06
● 2026-05-10 10:26:02
○NSns1.dsredirection.com2008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 11:27:40
○ 2015-10-16 21:46:36
○ 2026-05-10 10:26:02
○NSns1.dynadot.com2020-01-15 → 2020-01-15 · 4 obs
○ 2017-03-13 17:18:10
● 2020-01-15 08:00:52
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○NSns1637.ztomy.com2017-03-13 → 2017-03-13 · 4 obs
○ 2016-04-26 02:34:20
● 2017-03-13 17:18:10
○ 2020-01-15 08:00:52
○ 2026-05-10 10:26:02
○NSns2.dsredirection.com2008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 11:27:40
○ 2015-10-16 21:46:36
○ 2026-05-10 10:26:02
○NSns2.dynadot.com2020-01-15 → 2020-01-15 · 4 obs
○ 2017-03-13 17:18:10
● 2020-01-15 08:00:52
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○NSns2637.ztomy.com2017-03-13 → 2017-03-13 · 4 obs
○ 2016-04-26 02:34:20
● 2017-03-13 17:18:10
○ 2020-01-15 08:00:52
○ 2026-05-10 10:26:02
○NSsell.internettraffic.com2015-10-16 → 2016-04-26 · 5 obs
○ 2008-03-20 11:27:40
● 2015-10-16 21:46:36
● 2016-04-26 02:34:20
○ 2017-03-13 17:18:10
○ 2026-05-10 10:26:02
○A204.11.56.372017-03-13 → 2017-03-13 · 4 obs
○ 2016-04-26 02:34:20
● 2017-03-13 17:18:10
○ 2020-01-15 08:00:52
○ 2026-05-10 10:26:02
○A208.73.212.122008-03-20 → 2008-03-20 · 3 obs
● 2008-03-20 11:27:40
○ 2015-10-16 21:46:36
○ 2026-05-10 10:26:02
○A34.202.122.772020-01-15 → 2020-01-15 · 4 obs
○ 2017-03-13 17:18:10
● 2020-01-15 08:00:52
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○A35.169.225.2482020-01-15 → 2020-01-15 · 4 obs
○ 2017-03-13 17:18:10
● 2020-01-15 08:00:52
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○A52.0.7.302020-01-15 → 2020-01-15 · 4 obs
○ 2017-03-13 17:18:10
● 2020-01-15 08:00:52
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○A69.172.201.1532016-04-26 → 2016-04-26 · 4 obs
○ 2016-02-06 13:05:30
● 2016-04-26 02:34:20
○ 2017-03-13 17:18:10
○ 2026-05-10 10:26:02
○A69.172.201.2082015-10-16 → 2016-02-06 · 5 obs
○ 2008-03-20 11:27:40
● 2015-10-16 21:46:36
● 2016-02-06 13:05:30
○ 2016-04-26 02:34:20
○ 2026-05-10 10:26:02
○CNAME77980.bodis.com2026-03-28 → 2026-05-10 · 2 obs
○ 2026-03-28 14:22:06
○ 2026-05-10 10:26:02
○PTRns1637.ztomy.com2017-03-13 → 2017-03-13 · 3 obs
● 2017-03-13 17:18:10
○ 2020-01-15 08:00:52
○ 2026-05-10 10:26:02

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comd.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net...-
nevadaforum.comdns1.registrar-servers.com, dns2.registrar-servers.com4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

No DNSKEY for nevadaforum.com

⏱️ Timing

Total: 203ms | Queries: -

📄 Records

TypeCountSample Data
NS2dns1.registrar-servers.com, dns2.registrar-servers.com
SOA1dns1.registrar-servers.com hostmaster.re

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

Name Servers

nevadaforum.com is delegated to two name servers dns1.registrar-servers.com and dns2.registrar-servers.com.

nevadaforum.com shares the same name server setup as other domains, for instance primasign.com, car-rims.com, uhin.net, sandoneproductions.com and physicallylogicalquagga.cyou.

nevadaforum.com shares at least some name servers with other domains, for example giliyardo.com, liftmastergateoperators.com and envision-rx.com.

These name servers are commonly used with dns4.registrar-servers.com, dns3.registrar-servers.com and dns5.registrar-servers.com.

Host names with two IP numbers:

The host name dns1.registrar-servers.com points to 2610:a1:1024::200 and 156.154.132.200; the host name dns2.registrar-servers.com points to 2610:a1:1025::200 and 156.154.133.200.