`weddingmessenger.com`

DNSSEC	⚠️ Not signed
NS	`ns-1538.awsdns-00.co.uk` ⭐
		A	2600:9000:5306:200::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1538.awsdns-00.co.uk`
		A	205.251.198.2^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1538.awsdns-00.co.uk`
NS	`ns-1496.awsdns-59.org`
		A	2600:9000:5305:d800::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1496.awsdns-59.org`
		A	205.251.197.216^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1496.awsdns-59.org`
NS	`ns-454.awsdns-56.com`
		A	2600:9000:5301:c600::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-454.awsdns-56.com`
		A	205.251.193.198^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-454.awsdns-56.com`
NS	`ns-683.awsdns-21.net`
		A	2600:9000:5302:ab00::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-683.awsdns-21.net`
		A	205.251.194.171^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-683.awsdns-21.net`
SOA	`ns-1538.awsdns-00.co.uk`awsdns-hostmaster@amazon.com serial=1

`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.net`nstld@verisign-grs.com serial=1776082522

Same first word

weddingmessenger.com

DNS History

4 records (4 active, 0 former)

●NSns-1496.awsdns-59.org2016-07-12 → 2026-04-13 · 2 obs

● 2016-07-12 01:01:38
● 2026-04-13 12:32:10

●NSns-1538.awsdns-00.co.uk2016-07-12 → 2026-04-13 · 2 obs

● 2016-07-12 01:01:38
● 2026-04-13 12:32:10

●NSns-454.awsdns-56.com2016-07-12 → 2026-04-13 · 2 obs

● 2016-07-12 01:01:38
● 2026-04-13 12:32:10

●NSns-683.awsdns-21.net2016-07-12 → 2026-04-13 · 2 obs

● 2016-07-12 01:01:38
● 2026-04-13 12:32:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
weddingmessenger.com	ns-683.awsdns-21.net, ns-454.awsdns-56.com, ns-1538.awsdns-00.co.uk, ns-1496.awsdns-59.org	1 record

✅ Authoritative Response

Server:205.251.197.216

NS records: ns-683.awsdns-21.net, ns-454.awsdns-56.com, ns-1538.awsdns-00.co.uk, ns-1496.awsdns-59.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingmessenger.com (unsigned zone)

⏱️ Timing

Total: 231ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1496.awsdns-59.org, ns-1538.awsdns-00.co.uk...`
SOA	1	`ns-1538.awsdns-00.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-454.awsdns-56.com)

Analysis

Name Servers

weddingmessenger.com delegates to four name servers: ns-454.awsdns-56.com, ns-683.awsdns-21.net, ns-1496.awsdns-59.org and ns-1538.awsdns-00.co.uk.

weddingmessenger.com at least partially shares name servers with other domains, including eiteevth7k.com, agilexm.com, wakamono.jp, esse-ai.com and camelbak.info.

These name servers are commonly used with ns-80.awsdns-10.com, ns-869.awsdns-44.net and ns-1892.awsdns-44.co.uk.

Host names with two IP numbers: ns-454.awsdns-56.com points to 2600:9000:5301:c600::1 and 205.251.193.198; ns-683.awsdns-21.net points to 2600:9000:5302:ab00::1 and 205.251.194.171; ns-1496.awsdns-59.org points to 2600:9000:5305:d800::1 and 205.251.197.216; ns-1538.awsdns-00.co.uk points to 2600:9000:5306:200::1 and 205.251.198.2.

weddingmessenger.com - robtex.com