`planningforwedding.com`

DNSSEC	⚠️ Not signed
NS	`ns3.secureparkme.com` ⚠️ Not in zone NS records
		A	2a00:fd80:aaaa:ffff::bbbb:1^{🇦🇪 DREAMSCAPE-AS-AP2a00:fd80:aaaa::/48 AS38719 IPv6 Anycast Prefix}
			PTR	`ns1.ds.network`
		A	27.124.125.1^{🇦🇺 DREAMSCAPE-AS-AP27.124.125.0/24 Dreamscape Networks PTY LTD Suite 4.07 247 Coward Street}
			PTR	`ns1.ds.network`
NS	`ns4.secureparkme.com` ⚠️ Not in zone NS records
		A	2a00:fd80:aaaa:ffff::bbbb:2^{🇦🇪 DREAMSCAPE-AS-AP2a00:fd80:aaaa::/48 AS38719 IPv6 Anycast Prefix}
			PTR	`ns2.ds.network`
		A	27.124.125.2^{🇦🇺 DREAMSCAPE-AS-AP27.124.125.0/24 Dreamscape Networks PTY LTD Suite 4.07 247 Coward Street}
			PTR	`ns2.ds.network`

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

Same first word

planningforwedding.com

DNS History

5 records (2 active, 3 former)

○NSns1.yourhostingaccount.com2015-08-06 → 2016-06-20 · 4 obs

● 2015-08-06 04:31:38
● 2016-06-20 14:13:34
○ 2026-03-01 21:16:00
○ 2026-04-13 20:58:52

○NSns2.yourhostingaccount.com2015-08-06 → 2016-06-20 · 4 obs

● 2015-08-06 04:31:38
● 2016-06-20 14:13:34
○ 2026-03-01 21:16:00
○ 2026-04-13 20:58:52

●NSns3.secureparkme.com2026-03-01 → 2026-04-13 · 3 obs

○ 2016-06-20 14:13:34
● 2026-03-01 21:16:00
● 2026-04-13 20:58:52

●NSns4.secureparkme.com2026-03-01 → 2026-04-13 · 3 obs

○ 2016-06-20 14:13:34
● 2026-03-01 21:16:00
● 2026-04-13 20:58:52

○A141.8.225.2372015-08-06 → 2016-06-20 · 4 obs

● 2015-08-06 04:31:38
● 2016-06-20 14:13:34
○ 2026-03-01 21:16:00
○ 2026-04-13 20:58:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net...	-
planningforwedding.com	ns3.secureparkme.com, ns4.secureparkme.com	4 records

✅ Authoritative Response

Server:27.124.125.2

NS records: ns3.secureparkme.com, ns4.secureparkme.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for planningforwedding.com (unsigned zone)

⏱️ Timing

Total: 746ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns3.secureparkme.com, ns3.secureparkme.com, ns4.secureparkme.com...)

Analysis

Name Servers

planningforwedding.com's delegation uses two name servers, ns3.secureparkme.com and ns4.secureparkme.com.

planningforwedding.com shares the same name server setup as other domains, for example iarc.com.au, epo.net.au, thedentaltouch.com.au, pubsnearme.com.au and listerhouseclinic.com.au.

planningforwedding.com at least partially shares name servers with other domains, including nusyaayampenyet.my, neo.co.nz, dubbey.co.nz, middlefield.com.au and jscomputertechnology.com.au.

these name servers are commonly used with ns1.syrahost.com, ns2.syrahost.com, ns3.parkme.com.au and ns4.parkme.com.au.

Host names with two IPs:

ns3.secureparkme.com points to: 2a00:fd80:aaaa:ffff::bbbb:1 and 27.124.125.1

ns4.secureparkme.com points to: 2a00:fd80:aaaa:ffff::bbbb:2 and 27.124.125.2

planningforwedding.com - robtex.com