`galapesca.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3034::6815:4161^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
A	2606:4700:3034::ac43:a198^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
A	104.21.65.97^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
A	172.67.161.152^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns1.vultr.com` ⭐
		A	2001:19f0:ccc::1^{🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1}
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns1.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns2.wpdns.host`
		A	2001:19f0:ccd::2^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns2.vultr.com`
		A	173.199.96.97^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns2.vultrusercontent.com`
NS	`ns3.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
SOA	`ns1.vultr.com`dnsadm@choopa.com serial=0

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

Previously MX for

galapesca.com

Same first word

galapesca.com

galapesca.wpmudev.host

Similar names

gaspalace.com

galaspace.com

DNS History

19 records (8 active, 11 former)

○NSeric.ns.cloudflare.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
○ 2026-08-02 10:06:08
○ 2026-08-03 03:54:08

○NSetta.ns.cloudflare.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
○ 2026-08-02 10:06:08
○ 2026-08-03 03:54:08

●NSns1.vultr.com2026-08-02 → 2026-08-03 · 3 obs

○ 2026-02-15 19:19:38
● 2026-08-02 10:06:08
● 2026-08-03 03:54:08

●NSns1.wpdns.host2026-08-02 → 2026-08-03 · 3 obs

○ 2026-02-15 19:19:38
● 2026-08-02 10:06:08
● 2026-08-03 03:54:08

●NSns2.wpdns.host2026-08-02 → 2026-08-03 · 3 obs

○ 2026-02-15 19:19:38
● 2026-08-02 10:06:08
● 2026-08-03 03:54:08

●NSns3.wpdns.host2026-08-02 → 2026-08-03 · 3 obs

○ 2026-02-15 19:19:38
● 2026-08-02 10:06:08
● 2026-08-03 03:54:08

○NSns43.domaincontrol.com2016-04-24 → 2017-10-05 · 5 obs

○ 2016-02-05 05:11:42
● 2016-04-24 22:14:02
● 2017-10-05 21:36:44
○ 2026-02-15 19:19:38
○ 2026-08-03 03:54:08

○NSns44.domaincontrol.com2016-04-24 → 2017-10-05 · 5 obs

○ 2016-02-05 05:11:42
● 2016-04-24 22:14:02
● 2017-10-05 21:36:44
○ 2026-02-15 19:19:38
○ 2026-08-03 03:54:08

○NSns61.domaincontrol.com2015-07-04 → 2016-02-05 · 4 obs

● 2015-07-04 14:37:36
● 2016-02-05 05:11:42
○ 2016-04-24 22:14:02
○ 2026-08-03 03:54:08

○NSns62.domaincontrol.com2015-11-13 → 2016-02-05 · 5 obs

○ 2015-07-04 14:37:36
● 2015-11-13 11:04:02
● 2016-02-05 05:11:42
○ 2016-04-24 22:14:02
○ 2026-08-03 03:54:08

○MXgalapesca.com2015-11-13 → 2016-02-05 · 4 obs

● 2015-11-13 11:04:02
● 2016-02-05 05:11:42
○ 2016-04-24 22:14:02
○ 2026-08-03 03:54:08

○MXmail.galapesca.com2016-04-24 → 2026-02-17 · 5 obs

○ 2016-02-05 05:11:42
● 2016-04-24 22:14:02
● 2026-02-17 08:06:52
○ 2026-02-18 01:55:22
○ 2026-08-03 03:54:08

●A104.21.65.972026-02-15 → 2026-08-03 · 3 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
● 2026-08-03 03:54:08

●A172.67.161.1522026-02-15 → 2026-08-03 · 3 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
● 2026-08-03 03:54:08

○A192.124.249.1632016-04-24 → 2017-10-05 · 5 obs

○ 2016-02-05 05:11:42
● 2016-04-24 22:14:02
● 2017-10-05 21:36:44
○ 2026-02-15 19:19:38
○ 2026-08-03 03:54:08

○A23.229.137.682015-07-04 → 2016-02-05 · 4 obs

● 2015-07-04 14:37:36
● 2016-02-05 05:11:42
○ 2016-04-24 22:14:02
○ 2026-08-03 03:54:08

○A2606:4700:3031::ac43:a1982026-02-15 → 2026-02-15 · 4 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
○ 2026-07-08 16:12:02
○ 2026-08-03 03:54:08

●A2606:4700:3034::6815:41612026-02-15 → 2026-08-03 · 3 obs

○ 2017-10-05 21:36:44
● 2026-02-15 19:19:38
● 2026-08-03 03:54:08

●A2606:4700:3034::ac43:a1982026-07-08 → 2026-08-03 · 3 obs

○ 2026-02-15 19:19:38
● 2026-07-08 16:12:02
● 2026-08-03 03:54:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net...	-
galapesca.com	ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host	-

✅ Authoritative Response

Server:173.199.96.96

NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for galapesca.com (unsigned zone)

⏱️ Timing

Total: 490ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.65.97, 172.67.161.152`
AAAA	2	`2606:4700:3034::6815:4161, 2606:4700:3034::ac43:a198`
NS	3	`ns1.wpdns.host, ns3.wpdns.host...`
SOA	1	`ns1.vultr.com dnsadm.choopa.com`

Analysis

IP Addresses

galapesca.com resolves to four IP addresses: 104.21.65.97, 172.67.161.152, 2606:4700:3034::6815:4161 and 2606:4700:3034::ac43:a198.

Additional host names — aoyijianke.com, allplasta.com.au, naval-air.org and two others — share IP numbers with galapesca.com.

Name Servers

galapesca.com has four authoritative name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

galapesca.com has at least partial name server overlap with other domains, such as act4all.com, maineyouthleadership.org, brightoncrossings.com and two others.

It is common to find these name servers paired with the name servers ns2.vultr.com.

Host names with three IP numbers:

ns1.vultr.com resolves to three addresses: 173.199.96.96, 2001:19f0:ccc::1 and 2001:19f0:ccd::1.

Host names with two IP numbers:

ns1.wpdns.host maps to two IP addresses — 173.199.96.96 and 2001:19f0:ccd::1.

ns2.wpdns.host maps to two IP addresses — 173.199.96.97 and 2001:19f0:ccd::2.

ns3.wpdns.host maps to two IP addresses — 173.199.96.96 and 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 173.199.96.96.