washingtonfm.com - robtex.com

washingtonfm.com

DNSSEC⚠️ Not signed
A192.64.119.43🇺🇸 NAMCHEAP-PH192.64.119.0/24 Namecheap, Inc. 11400 W. Olympic Blvd. Suite 200 Los Angeles, CA 90064 UNITED STATES
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=1771343737

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=1771291435

Same first word

washingtonfm.com

DNS History

14 records (3 active, 11 former)

2017201820192020202120222023202420252026NSdns1.registrar-servers.comdns2.registrar-servers.comredbusprimarydns.washingtonfm.comredbussecondarydns.washingtonfm.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA192.64.119.43195.149.84.100195.149.84.1012001:67c:38c::642001:67c:38c::65
●NSdns1.registrar-servers.com2026-02-15 → 2026-03-23 · 3 obs
○ 2017-02-10 09:57:00
● 2026-02-15 11:23:20
● 2026-03-23 08:04:48
●NSdns2.registrar-servers.com2026-02-15 → 2026-03-23 · 3 obs
○ 2017-02-10 09:57:00
● 2026-02-15 11:23:20
● 2026-03-23 08:04:48
○NSredbusprimarydns.washingtonfm.com2016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48
○NSredbussecondarydns.washingtonfm.com2016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48
○MXeforward1.registrar-servers.com2026-02-15 → 2026-02-16 · 4 obs
● 2026-02-15 11:23:20
● 2026-02-16 22:10:08
○ 2026-03-08 05:04:08
○ 2026-03-23 08:04:48
○MXeforward2.registrar-servers.com2026-02-15 → 2026-02-16 · 4 obs
● 2026-02-15 11:23:20
● 2026-02-16 22:10:08
○ 2026-03-08 05:04:08
○ 2026-03-23 08:04:48
○MXeforward3.registrar-servers.com2026-02-15 → 2026-02-16 · 4 obs
● 2026-02-15 11:23:20
● 2026-02-16 22:10:08
○ 2026-03-08 05:04:08
○ 2026-03-23 08:04:48
○MXeforward4.registrar-servers.com2026-02-15 → 2026-02-16 · 4 obs
● 2026-02-15 11:23:20
● 2026-02-16 22:10:08
○ 2026-03-08 05:04:08
○ 2026-03-23 08:04:48
○MXeforward5.registrar-servers.com2026-02-15 → 2026-02-16 · 4 obs
● 2026-02-15 11:23:20
● 2026-02-16 22:10:08
○ 2026-03-08 05:04:08
○ 2026-03-23 08:04:48
●A192.64.119.432026-02-15 → 2026-03-23 · 3 obs
○ 2017-02-10 09:57:00
● 2026-02-15 11:23:20
● 2026-03-23 08:04:48
○A195.149.84.1002016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48
○A195.149.84.1012016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48
○A2001:67c:38c::642016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48
○A2001:67c:38c::652016-02-11 → 2017-02-10 · 4 obs
● 2016-02-11 11:07:18
● 2017-02-10 09:57:00
○ 2026-02-15 11:23:20
○ 2026-03-23 08:04:48

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
washingtonfm.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

⚠️ Insecure (no DNSSEC)

No DS record for washingtonfm.com (unsigned zone)

⏱️ Timing

Total: 161ms | Queries: -

📄 Records

TypeCountSample Data
A1192.64.119.43
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

IP Addresses

washingtonfm.com resolves to a single IP: 192.64.119.43.

Other host names, for instance danring.me, cognatechem.com, fawlc.com, hiphop-weekly.com and voood.com share IP numbers with washingtonfm.com.

Name Servers

washingtonfm.com has two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.

washingtonfm.com shares the same name server setup as other domains, for example artiiki.net, nategrams.com, katvids.com, ndtlbk.com and friio.com.

washingtonfm.com shares some name servers with other domains, for example travsd.com, kazoorecords.com, myriadtv.com, truput.net and lapwingpublications.com.

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

Host names with two IP numbers:

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