mcsdistrict.net - robtex.com
mcsdistrict.net
net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774438187 | ||||||
Subdomains
www.mcsdistrict.net |
Same first word
mcsdistrict.com |
mcsdistrict.org |
mcsdistrict.net |
DNS History
10 records (10 active, 0 former)
●NSns-cloud-a1.googledomains.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●NSns-cloud-a2.googledomains.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●NSns-cloud-a3.googledomains.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●NSns-cloud-a4.googledomains.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●MXalt1.aspmx.l.google.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●MXalt2.aspmx.l.google.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●MXalt3.aspmx.l.google.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●MXalt4.aspmx.l.google.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●MXaspmx.l.google.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
●A34.238.178.1412026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 11:55:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| mcsdistrict.net | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.34.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 623ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.238.178.141 |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a3.googledomains.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
Analysis
Hierarchy
mcsdistrict.net is a parent of www.mcsdistrict.net.
IP Addresses
mcsdistrict.net points to a single IP address: 34.238.178.141.
Other host names such as mail.sparta.org, msmusd.org, mail.agsd.us, bluehillschools.org and spart5.net share IP numbers with mcsdistrict.net.
Name Servers
mcsdistrict.net is delegated to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
At least part of the name servers for mcsdistrict.net are shared with other domains, for instance abciel.com, pendomonium.com, easynms.com, cheshirekow.com and sloansteddy.com.
Host names with two IP numbers:
ns-cloud-a1.googledomains.com points to: 2001:4860:4802:32::6a and 216.239.32.106
ns-cloud-a2.googledomains.com points to: 2001:4860:4802:34::6a and 216.239.34.106
ns-cloud-a3.googledomains.com points to: 2001:4860:4802:36::6a and 216.239.36.106
ns-cloud-a4.googledomains.com points to: 2001:4860:4802:38::6a and 216.239.38.106
Mail Servers
mcsdistrict.net 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.
mcsdistrict.net shares at least some mail servers with other domains, for example ns500671.ns500731.ns500742.ns500742.ns500671.ns500731.ns500742.ns500688.ns500705.ns500671.ns500671.ns500291.ns500153.tenderladiesbz.com, ns500699.ns500693.ns500734.ns500699.ns500699.ns500693.ns500699.ns500699.ns500693.ns500699.ns500632.ns500632.ns500632.ns500632.ns500110.dtrkdll.com, ns500765.ns500693.ns500693.ns500734.ns500699.ns500699.ns500734.ns500588.ns500699.ns500588.ns500699.ns500588.ns500632.ns500578.ns500110.dtrkdll.com, ns500765.ns500734.ns500699.ns500734.ns500693.ns500734.ns500699.ns500693.ns500699.ns500699.ns500588.ns500693.ns500588.ns500588.dtrkdll.com and ns500693.ns500693.ns500693.ns500693.ns500699.ns500734.ns500699.ns500734.ns500588.ns500588.ns500699.ns500693.ns500588.ns500588.ns500683.ns500110.dtrkdll.com.
These mail servers are commonly used alongside 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:4023:c0b::1a and 142.250.141.27; alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1b and 192.178.128.26; alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1b and 172.253.135.26; alt3.aspmx.l.google.com points to 2a00:1450:4001:c21::1a and 142.251.127.26; alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1b and 173.194.76.26.