district34.net - robtex.com
district34.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=1771291465 | ||||||
Same first word
district34.net |
district34.com |
Similar names
DNS History
7 records (3 active, 4 former)
●NSdns1.registrar-servers.com2026-03-23 → 2026-03-24 · 3 obs
● 2026-03-23 14:45:22
● 2026-03-24 05:34:48
●NSdns2.registrar-servers.com2026-03-23 → 2026-03-24 · 3 obs
● 2026-03-23 14:45:22
● 2026-03-24 05:34:48
○NSns1.parkingcrew.net2015-10-21 → 2016-04-18 · 4 obs
● 2016-04-18 01:21:30
○ 2016-11-19 16:40:44
○ 2026-03-24 05:34:48
○NSns2.parkingcrew.net2015-10-21 → 2016-04-18 · 4 obs
● 2016-04-18 01:21:30
○ 2016-11-19 16:40:44
○ 2026-03-24 05:34:48
●MXdistrict34-net.mail.protection.outlook.com2026-03-23 → 2026-03-24 · 3 obs
● 2026-03-23 14:45:22
● 2026-03-24 05:34:48
○MXmail.h-email.net2015-10-21 → 2016-04-18 · 4 obs
● 2016-04-18 01:21:30
○ 2016-11-19 16:40:44
○ 2026-03-24 05:34:48
○A185.53.178.72015-10-21 → 2016-04-18 · 4 obs
● 2016-04-18 01:21:30
○ 2016-11-19 16:40:44
○ 2026-03-24 05:34:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net... | - |
| district34.net | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for district34.net (unsigned zone)
⏱️ Timing
Total: 2038ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 1 | district34-net.mail.protection.outlook.c |
| TXT | 2 | MS=ms40437915, v=spf1 include:spf.protection.outlook.co |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
Name Servers
district34.net is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
district34.net shares the same name server setup as kevyang.com, busycalm.com, vizwiz.org, indigenousvr.net and nodetoself.org.
district34.net at least partially shares name servers with other domains, for instance yardcatbeer.com, russpoldrack.org, lloyd.wtf, beastnode.in and acom-ks.com.
These name servers are commonly 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.
Mail Servers
district34.net is handled by a single mail server, district34-net.mail.protection.outlook.com.
Host name district34-net.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c803::, 2a01:111:f403:c922::, 2a01:111:f403:c92c::3, 2a01:111:f403:f90f::, 52.101.10.5, 52.101.11.19, 52.101.40.24 and 52.101.194.4.