fairviewfiredistrict.org - robtex.com
fairviewfiredistrict.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1778431972 | ||||||
Same first word
fairviewfiredistrict.org |
DNS History
10 records (9 active, 1 former)
●NSns01.domaincontrol.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●NSns02.domaincontrol.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●MXalt1.aspmx.l.google.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●MXalt2.aspmx.l.google.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●MXalt3.aspmx.l.google.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●MXalt4.aspmx.l.google.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
●MXaspmx.l.google.com2018-05-24 → 2026-05-10 · 2 obs
● 2026-05-10 17:05:44
○A204.232.176.2342018-05-24 → 2018-05-24 · 3 obs
○ 2026-02-20 01:48:06
○ 2026-05-10 17:05:44
●A52.32.196.2302026-02-20 → 2026-05-10 · 3 obs
● 2026-02-20 01:48:06
● 2026-05-10 17:05:44
●A52.70.155.2402026-02-20 → 2026-05-10 · 3 obs
● 2026-02-20 01:48:06
● 2026-05-10 17:05:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| fairviewfiredistrict.org | ns01.domaincontrol.com, ns02.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.100.1
NS records: ns01.domaincontrol.com, ns02.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fairviewfiredistrict.org (unsigned zone)
⏱️ Timing
Total: 495ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.32.196.230, 52.70.155.240 |
| NS | 2 | ns01.domaincontrol.com, ns02.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=YTC3s9asqxPnmSU |
| SOA | 1 | ns01.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
fairviewfiredistrict.org has two IP numbers: 52.32.196.230 and 52.70.155.240.
Other host names, for instance nfssd.org, pinonforestssd.gov, texanagcd.org, coachellavalleycemeterydistrict.gov and mail2.serranowater.org share IP numbers with fairviewfiredistrict.org.
Name Servers
fairviewfiredistrict.org's delegation uses two name servers: ns01.domaincontrol.com and ns02.domaincontrol.com.
fairviewfiredistrict.org uses the same name server setup as other domains, such as drleonardcoldwell.org, drscpa.net, speakeasyvintage.com, caseygerry.org and daconsult.com.
Host names with two IPs:
ns01.domaincontrol.com points to 2603:5:2140::1 and 97.74.100.1
ns02.domaincontrol.com points to 2603:5:2240::1 and 173.201.68.1
Mail Servers
fairviewfiredistrict.org is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
fairviewfiredistrict.org shares at least some mail servers with other domains, for example rocktteok.com, ns500698.ns500759.ns500759.ns500698.ns500735.ns500698.ns500735.ns500698.ns500736.ns500576.ns500576.ns500698.ns500652.ns500619.trackreceptor.com, ns500759.ns500758.ns500759.ns500758.ns500698.ns500735.ns500735.ns500698.ns500708.ns500698.ns500708.trackreceptor.com, cavagro.com and planarp.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4004:c17::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to: 2800:3f0:4003:c0f::1b and 108.177.123.27.
alt2.aspmx.l.google.com points to: 2a00:1450:4013:c1e::1a and 192.178.213.27.
alt3.aspmx.l.google.com points to: 2a00:1450:4009:c0f::1b and 192.178.223.27.
alt4.aspmx.l.google.com points to: 2a00:1450:400c:c00::1a and 173.194.76.27.