`posttelegramm.com.ws`

	DNSSEC	⚠️ Not signed
	A	202.4.48.211^{🇼🇸 VODAFONESAMOA-AS-AP202.4.48.0/24 Proxy-registered route object}

`com.ws`

	DNSSEC	⚠️ Not signed
	NS	`ns2.dns.ws` ⭐
	NS	`europe1.dnsnode.net`
	NS	`ns5.dns.ws`
	NS	`nsp.dnsnode.net`
	NS	`nsu.dnsnode.net`
	NS	`us3.dns.ws`
	NS	`us4.dns.ws`
	SOA	`ns2.dns.ws`hostmaster@ns2.dns.ws serial=2607140057

WOT: SAFE (99/100)

Same first word

posttelegramm.com.ph

posttelegramm.com

posttelegramm.com.ws

DNS History

1 record (1 active, 0 former)

●A202.4.48.2112026-04-29 → 2026-07-14 · 11 obs

● 2026-04-29 22:39:26
● 2026-04-30 01:40:40
○ 2026-04-30 10:56:34
● 2026-04-30 16:44:08
● 2026-05-03 03:56:34
○ 2026-05-03 12:35:26
● 2026-05-21 23:57:32
● 2026-06-17 12:09:12
○ 2026-06-17 15:51:34
● 2026-07-03 12:57:20
● 2026-07-14 21:17:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ws	a.dns.ws, s.dns.ws, ns2.dns.ws, ns5.dns.ws...	8 records

✅ Authoritative Response

Server:64.70.19.80

NS records: a.dns.ws, s.dns.ws, ns2.dns.ws, ns5.dns.ws, us3.dns.ws, us4.dns.ws

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 854ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.dns.ws, a.dns.ws, s.dns.ws...)

Analysis

IP Addresses

posttelegramm.com.ws resolves to one IP address: 202.4.48.211.

swwex.vedos.com.ws, (0x736578).com.ws, 52-85-71-107.lhr3.r.cloudfront.net.ws and two other host names share IP numbers with posttelegramm.com.ws.

posttelegramm.com.ws - robtex.com