telegram.nyc - robtex.com
telegram.nyc
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-179.awsdns-22.com ⭐ | ||||||
| A | 2600:9000:5300:b300::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront | ||||||
| PTR | ns-179.awsdns-22.com | ||||||
| A | 205.251.192.179🇺🇸 Amazon205.251.192.0/24 prefix | ||||||
| PTR | ns-179.awsdns-22.com | ||||||
| NS | ns-1420.awsdns-49.org | ||||||
| A | 2600:9000:5305:8c00::1🇺🇸 Amazon2600:9000:5305::/48 - CloudFront | ||||||
| PTR | ns-1420.awsdns-49.org | ||||||
| A | 205.251.197.140🇺🇸 Amazon205.251.197.0/24 prefix | ||||||
| PTR | ns-1420.awsdns-49.org | ||||||
| NS | ns-1998.awsdns-57.co.uk | ||||||
| A | 2600:9000:5307:ce00::1🇺🇸 Amazon2600:9000:5307::/48 - CloudFront | ||||||
| PTR | ns-1998.awsdns-57.co.uk | ||||||
| A | 205.251.199.206🇺🇸 Amazon205.251.199.0/24 prefix | ||||||
| PTR | ns-1998.awsdns-57.co.uk | ||||||
| NS | ns-952.awsdns-55.net | ||||||
| A | 2600:9000:5303:b800::1🇺🇸 Amazon2600:9000:5303::/48 - CloudFront | ||||||
| PTR | ns-952.awsdns-55.net | ||||||
| A | 205.251.195.184🇺🇸 Amazon205.251.195.0/24 prefix | ||||||
| PTR | ns-952.awsdns-55.net | ||||||
| SOA | ns-179.awsdns-22.comawsdns-hostmaster@amazon.com serial=1 | ||||||
nyc
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns1.dns.nic.nyc ⭐ | ||||||
| NS | a.nic.nyc | ||||||
| NS | b.nic.nyc | ||||||
| NS | c.nic.nyc | ||||||
| NS | ns2.dns.nic.nyc | ||||||
| NS | ns3.dns.nic.nyc | ||||||
| SOA | ns1.dns.nic.nycadmin@tldns.godaddy serial=1778830747 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSns-1420.awsdns-49.org2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 08:42:38
●NSns-179.awsdns-22.com2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 08:42:38
●NSns-1998.awsdns-57.co.uk2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 08:42:38
●NSns-952.awsdns-55.net2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 08:42:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| nyc | ns2.dns.nic.nyc, ns1.dns.nic.nyc, a.nic.nyc, c.nic.nyc... | 12 records |
| telegram.nyc | ns-179.awsdns-22.com, ns-952.awsdns-55.net, ns-1420.awsdns-49.org, ns-1998.awsdns-57.co.uk | - |
✅ Authoritative Response
Server:205.251.199.206
NS records: ns-179.awsdns-22.com, ns-952.awsdns-55.net, ns-1420.awsdns-49.org, ns-1998.awsdns-57.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram.nyc (unsigned zone)
⏱️ Timing
Total: 583ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1420.awsdns-49.org, ns-179.awsdns-22.com... |
| SOA | 1 | ns-179.awsdns-22.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (ns3.dns.nic.nyc, ns2.dns.nic.nyc, ns1.dns.nic.nyc...)
Analysis
Name Servers
telegram.nyc is delegated to four name servers: ns-179.awsdns-22.com, ns-952.awsdns-55.net, ns-1420.awsdns-49.org and ns-1998.awsdns-57.co.uk.
telegram.nyc at least partially shares name servers with other domains, for instance d13hc4rsp6iv99.cloudfront.net, paywalls.com, d1i9xvk93k0dqw.cloudfront.net, minnesota.awsapps.com and addsubs.com.
Host names with two IP numbers:
ns-179.awsdns-22.com points to 2600:9000:5300:b300::1 and 205.251.192.179; ns-952.awsdns-55.net points to 2600:9000:5303:b800::1 and 205.251.195.184; ns-1420.awsdns-49.org points to 2600:9000:5305:8c00::1 and 205.251.197.140; ns-1998.awsdns-57.co.uk points to 2600:9000:5307:ce00::1 and 205.251.199.206.