`piercearchery.com`

DNSSEC	⚠️ Not signed
A	192.0.78.163^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.240^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns1.wordpress.com` ⭐
		A	2a04:fa87:ffff::c6b5:7409^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns1.wordpress.com`
		A	198.181.116.9^{🇺🇸 Automattic198.181.116.0/24 Route Object}
			PTR	`ns1.wordpress.com`
NS	`ns2.wordpress.com`
		A	2a04:fa87:ffff::c6b5:7509^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns2.wordpress.com`
		A	198.181.117.9^{🇺🇸 Automattic198.181.117.0/24 Route Object}
			PTR	`ns2.wordpress.com`
NS	`ns3.wordpress.com`
		A	2620:115:c00f::c000:4a09^{🇺🇸 Automattic2620:115:c00f::/48 Route6 Object}
			PTR	`ns3.wordpress.com`
		A	192.0.74.9^{🇺🇸 Automattic192.0.74.0/24 Route Object}
			PTR	`ns3.wordpress.com`
MX	`mx1.titan.email` ⭐
		A	3.218.119.224^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-218-119-224.compute-1.amazonaws.com`
		A	52.23.107.59^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-23-107-59.compute-1.amazonaws.com`
		A	52.72.144.152^{🇺🇸 Amazon52.72.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-72-144-152.compute-1.amazonaws.com`
MX	`mx2.titan.email`⁽²⁰⁾
		A	3.218.119.224^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-218-119-224.compute-1.amazonaws.com`
		A	52.23.107.59^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
			PTR	`ec2-52-23-107-59.compute-1.amazonaws.com`
		A	52.72.144.152^{🇺🇸 Amazon52.72.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-72-144-152.compute-1.amazonaws.com`
TXT	`v=spf1 include:spf.titan.email ~all`
TXT	`google-site-verification=gbq1Sh0OLzqqSAHjrt4WXjqTfyLE4unmaCmbQw7-8KU`
TXT	`v=spf1 include:spf.titan.email include:_spf.wpcloud.com ~all`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2005-07-18 #58

`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

Same first word

piercearchery.com

DNS History

10 records (7 active, 3 former)

○NSns01.domaincontrol.com2017-11-20 → 2017-11-20 · 3 obs

● 2017-11-20 20:16:12
○ 2026-03-14 17:23:24
○ 2026-03-23 11:37:18

○NSns02.domaincontrol.com2017-11-20 → 2017-11-20 · 3 obs

● 2017-11-20 20:16:12
○ 2026-03-14 17:23:24
○ 2026-03-23 11:37:18

●NSns1.wordpress.com2026-03-14 → 2026-03-23 · 3 obs

○ 2017-11-20 20:16:12
● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

●NSns2.wordpress.com2026-03-14 → 2026-03-23 · 3 obs

○ 2017-11-20 20:16:12
● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

●NSns3.wordpress.com2026-03-14 → 2026-03-23 · 3 obs

○ 2017-11-20 20:16:12
● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

●MXmx1.titan.email2026-03-14 → 2026-03-23 · 2 obs

● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

●MXmx2.titan.email2026-03-14 → 2026-03-23 · 2 obs

● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

○A184.168.221.612017-11-20 → 2017-11-20 · 3 obs

● 2017-11-20 20:16:12
○ 2026-03-14 17:23:24
○ 2026-03-23 11:37:18

●A192.0.78.1632026-03-14 → 2026-03-23 · 3 obs

○ 2017-11-20 20:16:12
● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

●A192.0.78.2402026-03-14 → 2026-03-23 · 3 obs

○ 2017-11-20 20:16:12
● 2026-03-14 17:23:24
● 2026-03-23 11:37:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net...	-
piercearchery.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:192.0.74.9

NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for piercearchery.com (unsigned zone)

⏱️ Timing

Total: 133ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.163, 192.0.78.240`
NS	3	`ns3.wordpress.com, ns1.wordpress.com...`
MX	2	`mx2.titan.email (pri: 20), mx1.titan.email (pri: 10)`
TXT	3	`v=spf1 include:spf.titan.email ~all, v=spf1 include:spf.titan.email include:_...`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)

Analysis

IP Addresses

piercearchery.com points to two IP numbers: 192.0.78.163 and 192.0.78.240.

Other host names, for instance perfectprimeco.com, highjewellerydream.com, foundry.vc, getiggy.com and help.plusmember.jp share IP numbers with piercearchery.com.

Name Servers

The domain piercearchery.com is delegated to three name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.

piercearchery.com shares name servers with other domains at least partially, for instance training-master.com, snecc.org, writingistestifying.com, henrytsangarchitect.com and timbersupplyco.com.

Host names with two IP numbers:

ns1.wordpress.com points to 2a04:fa87:ffff::c6b5:7409 and 198.181.116.9

ns2.wordpress.com points to 2a04:fa87:ffff::c6b5:7509 and 198.181.117.9

ns3.wordpress.com points to 2620:115:c00f::c000:4a09 and 192.0.74.9

Mail Servers

piercearchery.com is handled by two mail servers: mx1.titan.email and mx2.titan.email.

piercearchery.com shares the same mail server setup as other domains, including granfood.com.br, demko.com, assine-gap.conk.com.br, ankra.info and oliveirarodrigo.net.

piercearchery.com shares at least some mail servers with other domains, for instance fortitudefinance.com.au.

Host names with three IP numbers:

mx1.titan.email points to 3.218.119.224, 52.23.107.59 and 52.72.144.152; mx2.titan.email points to 3.218.119.224, 52.23.107.59 and 52.72.144.152.

Host names that point to 3.218.119.224: mx1.titan.email and mx2.titan.email.

Host names that point to 52.23.107.59: mx1.titan.email and mx2.titan.email.

Host names that point to 52.72.144.152: mx1.titan.email and mx2.titan.email.

piercearchery.com - robtex.com