`doublejwedding.com`

DNSSEC	⚠️ Not signed
A	15.197.212.58^{🇺🇸 Amazon15.197.208.0/20}
		PTR	`af1f69020f2387294.awsglobalaccelerator.com`
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
SOA	`dns1.name-services.com`info@name-services.com serial=1770692424

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

DNS History

29 records (6 active, 23 former)

●NSdns1.name-services.com2026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○NSdns1.p05.nsone.net2017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

●NSdns2.name-services.com2026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○NSdns2.p05.nsone.net2017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

●NSdns3.name-services.com2026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○NSdns3.p05.nsone.net2017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

●NSdns4.name-services.com2026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○NSdns4.p05.nsone.net2017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

●NSdns5.name-services.com2026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○NSns1.systemdns.com2016-06-21 → 2016-06-21 · 3 obs

● 2016-06-21 22:20:26
○ 2017-02-16 08:40:14
○ 2026-02-26 22:28:10

○NSns1.whoisdomain.kr2019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○NSns2.systemdns.com2016-06-21 → 2016-06-21 · 3 obs

● 2016-06-21 22:20:26
○ 2017-02-16 08:40:14
○ 2026-02-26 22:28:10

○NSns2.whoisdomain.kr2019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○NSns3.systemdns.com2016-06-21 → 2016-06-21 · 3 obs

● 2016-06-21 22:20:26
○ 2017-02-16 08:40:14
○ 2026-02-26 22:28:10

○NSns3.whoisdomain.kr2019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○NSns4.whoisdomain.kr2019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○MXdomain.not.configured2015-07-03 → 2015-07-03 · 3 obs

● 2015-07-03 23:02:16
○ 2016-02-06 06:55:04
○ 2026-02-26 22:28:10

●A15.197.212.582026-02-26 → 2026-02-26 · 2 obs

○ 2019-03-19 17:16:32
● 2026-02-26 22:28:10

○A185.199.108.1532019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A185.199.109.1532019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A185.199.110.1532019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A185.199.111.1532019-03-19 → 2019-03-19 · 3 obs

○ 2017-02-16 08:40:14
● 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A198.185.159.1442017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A198.185.159.1452016-06-21 → 2017-02-16 · 5 obs

○ 2016-02-06 06:55:04
● 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A198.49.23.1442017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A198.49.23.1452017-02-16 → 2017-02-16 · 4 obs

○ 2016-06-21 22:20:26
● 2017-02-16 08:40:14
○ 2019-03-19 17:16:32
○ 2026-02-26 22:28:10

○A54.235.159.972015-07-03 → 2015-07-03 · 3 obs

● 2015-07-03 23:02:16
○ 2015-11-18 12:13:18
○ 2026-02-26 22:28:10

○A69.64.147.2422015-11-18 → 2015-11-18 · 4 obs

○ 2015-07-03 23:02:16
● 2015-11-18 12:13:18
○ 2016-02-06 06:55:04
○ 2026-02-26 22:28:10

○PTRdomain.not.configured2015-07-03 → 2015-07-03 · 3 obs

● 2015-07-03 23:02:16
○ 2017-02-16 08:40:14
○ 2026-02-26 22:28:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net...	-
doublejwedding.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server: 216.40.47.202

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for doublejwedding.com (unsigned zone)

⏱️ Timing

Total: 101ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`15.197.212.58`
NS	5	`dns4.name-services.com, dns2.name-services.com...`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

AI analysis

doublejwedding.com points to an IP address: 15.197.212.58.

other host names include nitrexhosting.com, tr2p.com, contadormei.com, graficapontual.com and 101interviews.com; they share IP numbers with doublejwedding.com.

doublejwedding.com is delegated to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com and dns5.name-services.com.

doublejwedding.com at least partially shares name servers with other domains, for instance ungrantable.com, rtmpcontrol.com, mobilehotels.net, bfsok.com and tomofportland.com.

Host names with two IP numbers:

The host name dns1.name-services.com points to 2604:4000:2800:2000:64:98:148:137 and 64.98.148.137.

The host name dns2.name-services.com points to 2604:4000:0:d:216:40:47:201 and 216.40.47.201.

The host name dns3.name-services.com points to 2604:4000:2800:2000:64:98:148:138 and 64.98.148.138.

The host name dns4.name-services.com points to 2604:4000:0:d:216:40:47:202 and 216.40.47.202.

The host name dns5.name-services.com points to 2604:4000:2800:2000:64:98:148:139 and 64.98.148.139.

doublejwedding.com - robtex.com