`historicwedding.com`

DNSSEC	⚠️ Not signed
A	2600:9000:a612:55d9:1b82:e963:5969:d2c7^{🇺🇸 Amazon2600:9000:a600::/43}
		PTR	`ad988eeb126877ff9.dualstack.awsglobalaccelerator.com`
A	2a01:4f8:1c1e:d6f1::1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
A	2a01:4ff:f0:5f41::1^{🇺🇸 HETZNER-CLOUD2-AS2a01:4ff::/40 HETZNER-IPv6-BLK}
A	2a01:4ff:1f0:dd50::1^{🇩🇪 HETZNER-CLOUD3-AS2a01:4ff:100::/40 HETZNER-IPv6-BLK}
A	5.78.156.59^{🇺🇸 HETZNER-CLOUD3-AS5.78.156.0/24}
A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
A	46.62.237.138^{🇩🇪 Hetzner46.62.128.0/17 HETZNER-DC}
A	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
NS	`ns1.dns-redirect.com` ⭐
		A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
			PTR	`static.86.47.161.5.clients.your-server.de`
		A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
			PTR	`static.87.230.161.5.clients.your-server.de`
		A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
			PTR	`static.179.128.201.195.clients.your-server.de`
NS	`ns2.dns-redirect.com`
		A	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
		A	166.117.68.124^{🇺🇸 Amazon166.117.64.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
TXT	`95b3a950-315c-45b8-937a-b865ebeb043a`
TXT	`afternic-verification-aGHTsEA2nLa7KRqzmJySAx`
SOA	`ns1.dns-redirect.com`admin@redirhub.com 2024-07-29 #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=1776209442

Subdomains

mail.historicwedding.com

Same first word

historicwedding.com

DNS History

26 records (12 active, 14 former)

●NSns1.dns-redirect.com2026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

○NSns1.namebrightdns.com2015-05-23 → 2017-06-25 · 6 obs

● 2015-05-23 23:58:12
○ 2015-10-11 08:58:22
○ 2015-12-21 09:14:12
● 2016-03-23 15:53:06
● 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

●NSns2.dns-redirect.com2026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

○NSns2.namebrightdns.com2015-05-23 → 2017-06-25 · 3 obs

● 2015-05-23 23:58:12
● 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

○NSnsg1.namebrightdns.com2015-10-11 → 2015-12-21 · 5 obs

○ 2015-05-23 23:58:12
● 2015-10-11 08:58:22
● 2015-12-21 09:14:12
○ 2016-03-23 15:53:06
○ 2026-04-14 23:31:52

○MXanmail.namebrightmail.com2015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 23:58:12
○ 2015-10-11 08:58:22
○ 2026-04-14 23:31:52

○A107.23.160.2182015-12-21 → 2015-12-21 · 4 obs

○ 2015-10-11 08:58:22
● 2015-12-21 09:14:12
○ 2016-03-23 15:53:06
○ 2026-04-14 23:31:52

●A195.201.128.1792026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A2600:9000:a612:55d9:1b82:e963:5969:d2c72026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A2a01:4f8:1c1e:d6f1::12026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A2a01:4ff:1f0:dd50::12026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A2a01:4ff:f0:5f41::12026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A46.62.237.1382026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A5.161.230.872026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A5.161.47.862026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

●A5.78.156.592026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

○A52.21.180.2332016-03-23 → 2016-03-23 · 4 obs

○ 2015-12-21 09:14:12
● 2016-03-23 15:53:06
○ 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

○A52.3.120.902016-03-23 → 2016-03-23 · 4 obs

○ 2015-12-21 09:14:12
● 2016-03-23 15:53:06
○ 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

○A54.174.31.2542015-10-11 → 2015-10-11 · 4 obs

○ 2015-05-23 23:58:12
● 2015-10-11 08:58:22
○ 2015-12-21 09:14:12
○ 2026-04-14 23:31:52

○A54.208.74.2152015-10-11 → 2015-10-11 · 4 obs

○ 2015-05-23 23:58:12
● 2015-10-11 08:58:22
○ 2015-12-21 09:14:12
○ 2026-04-14 23:31:52

○A54.209.90.812015-12-21 → 2015-12-21 · 4 obs

○ 2015-10-11 08:58:22
● 2015-12-21 09:14:12
○ 2016-03-23 15:53:06
○ 2026-04-14 23:31:52

○A54.236.84.1112015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 23:58:12
○ 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

○A54.85.146.1862015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 23:58:12
○ 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

●A76.223.91.202026-04-14 → 2026-04-14 · 2 obs

○ 2017-06-25 16:07:24
● 2026-04-14 23:31:52

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-05-23 → 2016-03-23 · 4 obs

● 2015-05-23 23:58:12
● 2016-03-23 15:53:06
○ 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-06-25 → 2017-06-25 · 3 obs

○ 2016-03-23 15:53:06
● 2017-06-25 16:07:24
○ 2026-04-14 23:31:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, d.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net...	-
historicwedding.com	ns1.dns-redirect.com, ns2.dns-redirect.com	5 records

✅ Authoritative Response

Server:195.201.128.179

NS records: ns1.dns-redirect.com, ns2.dns-redirect.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for historicwedding.com (unsigned zone)

⏱️ Timing

Total: 328ms | Queries: -

📄 Records

Type	Count	Sample Data
A	6	`5.161.230.87, 46.62.237.138...`
AAAA	4	`2a01:4f8:1c1e:d6f1::1, 2600:9000:a612:55d9:1b82:e963:5969:d2c7...`
NS	2	`ns1.dns-redirect.com, ns2.dns-redirect.com`
TXT	2	`95b3a950-315c-45b8-937a-b865ebeb043a, afternic-verification-aGHTsEA2nLa7KRqzmJ`
SOA	1	`ns1.dns-redirect.com admin.redirhub.com`

📌 Glue Records Collected

Total: 5

Out-of-bailiwick: 5 (ns1.dns-redirect.com, ns1.dns-redirect.com, ns1.dns-redirect.com...)

Analysis

Hierarchy

historicwedding.com is parent of mail.historicwedding.com.

IP Addresses

Ten IP numbers are pointed to by historicwedding.com: 2600:9000:a612:55d9:1b82:e963:5969:d2c7, 2a01:4f8:1c1e:d6f1::1, 2a01:4ff:f0:5f41::1, 2a01:4ff:1f0:dd50::1, 5.78.156.59, 5.161.47.86, 5.161.230.87, 46.62.237.138, 76.223.91.20 and 195.201.128.179.

Other host names, for instance metawatchers.site, firstpave.com, techstrive-ni.com, www.creativemagazines.com and mediarelax.com share IP numbers with historicwedding.com.

Name Servers

historicwedding.com's delegation is to two name servers ns1.dns-redirect.com and ns2.dns-redirect.com.

historicwedding.com shares the same name server configuration as other domains, such as jardindeasia.com, index.php.bigip-dmz.cahayagemilangfurniture.com, clronline.com, bobo.email and mail.mfcenter.mobi.

Host names with three IP numbers:

ns1.dns-redirect.com points to 5.161.47.86, 5.161.230.87 and 195.201.128.179.

Host names with two IP numbers:

ns2.dns-redirect.com points to 76.223.91.20 and 166.117.68.124.

historicwedding.com - robtex.com