🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`programmaticconnect.com`

DNSSEC	⚠️ Not signed
A	192.0.78.173^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.215^{🇺🇸 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	`mx2.zoho.com` ⭐
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx3.zoho.com`⁽²⁰⁾
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx.zoho.com`⁽⁵⁰⁾
		A	204.141.43.44^{🇺🇸 ZohoAS204.141.42.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx6.zoho.com`
			PTR	`mx7.zoho.com`
			PTR	`mx8.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
TXT	`zoho-verification=zb80605260.zmverify.zoho.com`
TXT	`v=spf1 include:zoho.com 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=1794444981

Same first word

programmaticconnect.com

Previous names

Next names

DNS History

10 records (8 active, 2 former)

●NSns1.wordpress.com2017-08-13 → 2026-11-12 · 2 obs

● 2017-08-13 16:49:38
● 2026-11-12 01:06:48

●NSns2.wordpress.com2017-08-13 → 2026-11-12 · 2 obs

● 2017-08-13 16:49:38
● 2026-11-12 01:06:48

●NSns3.wordpress.com2017-08-13 → 2026-11-12 · 2 obs

● 2017-08-13 16:49:38
● 2026-11-12 01:06:48

●MXmx.zoho.com2026-09-05 → 2026-11-12 · 2 obs

● 2026-09-05 10:41:44
● 2026-11-12 01:06:48

●MXmx2.zoho.com2026-09-05 → 2026-11-12 · 2 obs

● 2026-09-05 10:41:44
● 2026-11-12 01:06:48

●MXmx3.zoho.com2026-09-05 → 2026-11-12 · 2 obs

● 2026-09-05 10:41:44
● 2026-11-12 01:06:48

●A192.0.78.1732026-09-05 → 2026-11-12 · 3 obs

○ 2017-08-13 16:49:38
● 2026-09-05 10:41:44
● 2026-11-12 01:06:48

●A192.0.78.2152026-09-05 → 2026-11-12 · 3 obs

○ 2017-08-13 16:49:38
● 2026-09-05 10:41:44
● 2026-11-12 01:06:48

○A192.0.78.242017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 16:49:38
○ 2026-09-05 10:41:44
○ 2026-11-12 01:06:48

○A192.0.78.252017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 16:49:38
○ 2026-09-05 10:41:44
○ 2026-11-12 01:06:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...	-
programmaticconnect.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:198.181.116.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for programmaticconnect.com (unsigned zone)

⏱️ Timing

Total: 380ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.173, 192.0.78.215`
NS	3	`ns2.wordpress.com, ns3.wordpress.com...`
MX	3	`mx2.zoho.com (pri: 20), mx3.zoho.com (pri: 50)...`
TXT	2	`zoho-verification=zb80605260.zmverify.zo, v=spf1 include:zoho.com include:_spf.wpc`
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

programmaticconnect.com points to the IP addresses 192.0.78.173 and 192.0.78.215

Two other host names, along with britthillphoto.com, visuora.de and manasmohanty.dev, also share IP numbers with programmaticconnect.com.

Name Servers

Three name servers are authoritative for programmaticconnect.com: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.

The name servers of programmaticconnect.com overlap at least partially with those of other domains — among them pemexdeerpark.com.mx, fmachronicles.com, talkingandteachingscience.com and two more.

ns1.wordpress.com resolves to 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409. ns2.wordpress.com resolves to 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509. ns3.wordpress.com resolves to 192.0.74.9 and 2620:115:c00f::c000:4a09. All three hostnames point to two IP numbers each.

Mail Servers

Mail for programmaticconnect.com is routed through three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.

There is at least a partial MX overlap between programmaticconnect.com and other domains, including admin.sa, wslconexiones.com, forestbrookdental.com and two others.

mx2.zoho.com, mx3.zoho.com and mx.zoho.com all resolve to 204.141.43.44, with each host carrying exactly one IP address.

Each of mx2.zoho.com, mx3.zoho.com and mx.zoho.com resolves to 204.141.43.44.

programmaticconnect.com - robtex.com