telegraphdistrict.com - robtex.com
telegraphdistrict.com
com
| 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=1771291435 | ||||||
DNS History
11 records (6 active, 5 former)
●NSns-1111.awsdns-10.org2026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
●NSns-1643.awsdns-13.co.uk2026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
●NSns-418.awsdns-52.com2026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
●NSns-669.awsdns-19.net2026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
○NSns47.domaincontrol.com2017-11-19 → 2017-11-19 · 3 obs
○ 2026-03-05 14:29:02
○ 2026-03-05 14:29:06
○NSns48.domaincontrol.com2017-11-19 → 2017-11-19 · 3 obs
○ 2026-03-05 14:29:02
○ 2026-03-05 14:29:06
○MXmailstore1.secureserver.net2017-11-19 → 2017-11-19 · 3 obs
○ 2026-03-05 14:29:02
○ 2026-03-05 14:29:06
○MXsmtp.secureserver.net2017-11-19 → 2017-11-19 · 3 obs
○ 2026-03-05 14:29:02
○ 2026-03-05 14:29:06
●A141.193.213.202026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
●A141.193.213.212026-03-05 → 2026-03-05 · 3 obs
● 2026-03-05 14:29:02
● 2026-03-05 14:29:06
○A52.40.81.2452017-11-19 → 2017-11-19 · 3 obs
○ 2026-03-05 14:29:02
○ 2026-03-05 14:29:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| telegraphdistrict.com | ns-669.awsdns-19.net, ns-418.awsdns-52.com, ns-1643.awsdns-13.co.uk, ns-1111.awsdns-10.org | 1 record |
✅ Authoritative Response
Server: 205.251.193.162
NS records: ns-669.awsdns-19.net, ns-418.awsdns-52.com, ns-1643.awsdns-13.co.uk, ns-1111.awsdns-10.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegraphdistrict.com (unsigned zone)
⏱️ Timing
Total: 721ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 141.193.213.21, 141.193.213.20 |
| NS | 4 | ns-1111.awsdns-10.org, ns-1643.awsdns-13.co.uk... |
| SOA | 1 | ns-669.awsdns-19.net awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 1
Out-of-bailiwick: 1 (ns-418.awsdns-52.com)
Analysis
IP Addresses
telegraphdistrict.com resolves to two IP numbers: 141.193.213.20 and 141.193.213.21.
Other host names, for instance hura.hr, incisive.com, greengiant.com, malorbooks.com and ns1.itskey.com share IP numbers with telegraphdistrict.com.
Name Servers
telegraphdistrict.com's delegation is handled by four name servers: ns-418.awsdns-52.com, ns-669.awsdns-19.net, ns-1111.awsdns-10.org and ns-1643.awsdns-13.co.uk.
telegraphdistrict.com partially shares name servers with other domains; examples include cinetixx.eu, theboostmate.com, qsure.com, care-pro.jp and creality3dofficial.com.
These name servers are commonly used with ns-1968.awsdns-54.co.uk, ns-1277.awsdns-31.org and ns-561.awsdns-06.net.
Host names with two IPs:
ns-418.awsdns-52.com points to 2600:9000:5301:a200::1 and 205.251.193.162
ns-669.awsdns-19.net points to 2600:9000:5302:9d00::1 and 205.251.194.157
ns-1111.awsdns-10.org points to 2600:9000:5304:5700::1 and 205.251.196.87
ns-1643.awsdns-13.co.uk points to 2600:9000:5306:6b00::1 and 205.251.198.107