`weddingplanery.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:5211^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::ac43:c16c^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.82.17^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.193.108^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ainsley.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:26d3^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2d3^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ainsley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22d3^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ainsley.ns.cloudflare.com`
		A	108.162.194.211^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	162.159.38.211^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
		A	172.64.34.211^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ainsley.ns.cloudflare.com`
NS	`huxley.ns.cloudflare.com`
		A	2606:4700:58::a29f:2cbc^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`huxley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3bc^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`huxley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23bc^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`huxley.ns.cloudflare.com`
		A	108.162.195.188^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`huxley.ns.cloudflare.com`
		A	162.159.44.188^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`huxley.ns.cloudflare.com`
		A	172.64.35.188^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`huxley.ns.cloudflare.com`
MX	`mx.stackmail.com` ⭐
		A	185.151.28.67^{🇬🇧 TWENTYI185.151.28.0/24}
			PTR	`mx.stackmail.com`
TXT	`v=spf1 include:spf.stackmail.com a mx -all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.82.17, 172.67.193.108
		IPv6 hints	2606:4700:3032::6815:5211, 2606:4700:3036::ac43:c16c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=158, name=cloudflare-ech.com
SOA	`ainsley.ns.cloudflare.com`dns@cloudflare.com serial=2402786649

`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=1778480076

Same first word

weddingplanery.com

DNS History

12 records (7 active, 5 former)

●NSainsley.ns.cloudflare.com2026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

●NShuxley.ns.cloudflare.com2026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

○NSns1.easyname.eu2015-08-23 → 2017-03-26 · 4 obs

● 2015-08-23 17:48:50
● 2017-03-26 09:32:26
○ 2026-05-04 19:22:56
○ 2026-05-11 06:29:08

○NSns2.easyname.eu2015-08-23 → 2017-03-26 · 4 obs

● 2015-08-23 17:48:50
● 2017-03-26 09:32:26
○ 2026-05-04 19:22:56
○ 2026-05-11 06:29:08

●MXmx.stackmail.com2026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

○MXmx01.easyname.eu2015-08-23 → 2017-03-26 · 4 obs

● 2015-08-23 17:48:50
● 2017-03-26 09:32:26
○ 2026-05-04 19:22:56
○ 2026-05-11 06:29:08

○MXmx02.easyname.eu2015-08-23 → 2017-03-26 · 4 obs

● 2015-08-23 17:48:50
● 2017-03-26 09:32:26
○ 2026-05-04 19:22:56
○ 2026-05-11 06:29:08

●A104.21.82.172026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

●A172.67.193.1082026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

●A2606:4700:3032::6815:52112026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

●A2606:4700:3036::ac43:c16c2026-05-04 → 2026-05-11 · 3 obs

○ 2017-03-26 09:32:26
● 2026-05-04 19:22:56
● 2026-05-11 06:29:08

○A77.244.243.532015-08-23 → 2017-03-26 · 4 obs

● 2015-08-23 17:48:50
● 2017-03-26 09:32:26
○ 2026-05-04 19:22:56
○ 2026-05-11 06:29:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
weddingplanery.com	ainsley.ns.cloudflare.com, huxley.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.188

NS records: ainsley.ns.cloudflare.com, huxley.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingplanery.com (unsigned zone)

⏱️ Timing

Total: 366ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.82.17, 172.67.193.108`
AAAA	2	`2606:4700:3036::ac43:c16c, 2606:4700:3032::6815:5211`
NS	2	`ainsley.ns.cloudflare.com, huxley.ns.cloudflare.com`
MX	1	`mx.stackmail.com (pri: 10)`
TXT	1	`v=spf1 include:spf.stackmail.com a mx -a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ainsley.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ainsley.ns.cloudflare.com, ainsley.ns.cloudflare.com, ainsley.ns.cloudflare.com...)

Analysis

IP Addresses

weddingplanery.com maps to four IP numbers: 2606:4700:3032::6815:5211, 2606:4700:3036::ac43:c16c, 104.21.82.17 and 172.67.193.108.

Other host names, for instance www.zenphi.dev, truhyaet5uet.online, aishu9995.com, discoadventures.com and j.uuu.cam share IP numbers with weddingplanery.com.

Name Servers

Two name servers ainsley.ns.cloudflare.com and huxley.ns.cloudflare.com handle delegation for weddingplanery.com.

weddingplanery.com uses the same name server setup as other domains, for example boundpr.com, nodeapp.org, crypto-trade.co, shaderapp.com and cpam2024.com.

weddingplanery.com partially shares name servers with other domains; examples include expormim.com, beallshome.com, eprocdata.com, shokusradio.com and polish-casino-online.com.

these name servers are commonly used with the name servers miles.ns.cloudflare.com.

Host names with six IP numbers: ainsley.ns.cloudflare.com points to: 2606:4700:50::a29f:26d3, 2803:f800:50::6ca2:c2d3, 2a06:98c1:50::ac40:22d3, 108.162.194.211, 162.159.38.211 and 172.64.34.211; huxley.ns.cloudflare.com points to: 2606:4700:58::a29f:2cbc, 2803:f800:50::6ca2:c3bc, 2a06:98c1:50::ac40:23bc, 108.162.195.188, 162.159.44.188 and 172.64.35.188.

Mail Servers

weddingplanery.com is handled by a single mail server, mx.stackmail.com.

weddingplanery.com has the same mail server setup as other domains, including anapoly.com, racketpages.com, akpfin.com, themonument.info and arizonacorporates.com.

mx.stackmail.com points to a single IP: 185.151.28.67.

weddingplanery.com - robtex.com