🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`processcontrolservices.com`

DNSSEC	⚠️ Not signed
A	151.101.1.124^{🇺🇸 Fastly151.101.0.0/22}
A	151.101.65.124^{🇺🇸 Fastly151.101.64.0/22}
A	151.101.129.124^{🇺🇸 Fastly151.101.128.0/22}
A	151.101.193.124^{🇺🇸 Fastly151.101.192.0/22}
NS	`ns1-34.azure-dns.com` ⭐
		A	2603:1061:0:10::22^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
		A	150.171.10.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
NS	`ns2-34.azure-dns.net`
		A	2620:1ec:8ec:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
		A	150.171.16.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
NS	`ns3-34.azure-dns.org`
		A	2a01:111:4000:10::22^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-34.azure-dns.org`
		A	13.107.222.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-34.azure-dns.org`
NS	`ns4-34.azure-dns.info`
		A	2620:1ec:bda:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
		A	13.107.206.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
MX	`us-smtp-inbound-1.mimecast.com` ⭐
		A	170.10.128.141^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.128.221^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.128.242^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.141^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.221^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.242^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
MX	`us-smtp-inbound-2.mimecast.com` ⭐
		A	170.10.128.141^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.128.221^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.128.242^{🇺🇸 Mimecast-NA170.10.128.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.141^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.221^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
		A	170.10.132.242^{🇺🇸 Mimecast-NA170.10.132.0/23 191 Spring St Lexington MA 02421 United States}
			PTR	`us-smtp-inbound-1.mimecast.com`
			PTR	`us-smtp-inbound-2.mimecast.com`
TXT	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all`
SOA	`ns1-34.azure-dns.com`azuredns-hostmaster@microsoft.com serial=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=1790806874

Same first word

processcontrolservices.com

Previous names

Next names

DNS History

24 records (10 active, 14 former)

○NSdns059.b.register.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

○NSdns123.a.register.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

○NSdns242.c.register.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

○NSdns249.d.register.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

●NSns1-34.azure-dns.com2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●NSns2-34.azure-dns.net2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●NSns3-34.azure-dns.org2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●NSns4-34.azure-dns.info2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

○NSns73.worldnic.com2015-11-20 → 2019-01-26 · 5 obs

○ 2015-06-19 16:16:44
● 2015-11-20 22:55:30
● 2019-01-26 15:21:56
○ 2026-09-23 22:02:12
○ 2026-09-30 22:38:56

○NSns74.worldnic.com2015-11-20 → 2019-01-26 · 5 obs

○ 2015-06-19 16:16:44
● 2015-11-20 22:55:30
● 2019-01-26 15:21:56
○ 2026-09-23 22:02:12
○ 2026-09-30 22:38:56

○MXmail01.fcxperformance.com2015-11-20 → 2016-04-25 · 5 obs

○ 2015-06-19 16:16:44
● 2015-11-20 22:55:30
● 2016-04-25 21:48:18
○ 2017-01-10 05:05:58
○ 2026-09-30 22:38:56

○MXmail02.fcxperformance.com2015-11-20 → 2016-04-25 · 5 obs

○ 2015-06-19 16:16:44
● 2015-11-20 22:55:30
● 2016-04-25 21:48:18
○ 2017-01-10 05:05:58
○ 2026-09-30 22:38:56

○MXmxa-0022ec01.gslb.pphosted.com2017-01-10 → 2019-01-26 · 5 obs

○ 2016-04-25 21:48:18
● 2017-01-10 05:05:58
● 2019-01-26 15:21:56
○ 2026-09-23 22:02:12
○ 2026-09-30 22:38:56

○MXmxb-0022ec01.gslb.pphosted.com2017-01-10 → 2019-01-26 · 5 obs

○ 2016-04-25 21:48:18
● 2017-01-10 05:05:58
● 2019-01-26 15:21:56
○ 2026-09-23 22:02:12
○ 2026-09-30 22:38:56

○MXprocesscontrolservices.com.1.arsmtp.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

○MXprocesscontrolservices.com.2.arsmtp.com2015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

●MXus-smtp-inbound-1.mimecast.com2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●MXus-smtp-inbound-2.mimecast.com2026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●A151.101.1.1242026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●A151.101.129.1242026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●A151.101.193.1242026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

●A151.101.65.1242026-09-23 → 2026-09-30 · 3 obs

○ 2019-01-26 15:21:56
● 2026-09-23 22:02:12
● 2026-09-30 22:38:56

○A198.0.110.1142015-06-19 → 2015-06-19 · 3 obs

● 2015-06-19 16:16:44
○ 2015-11-20 22:55:30
○ 2026-09-30 22:38:56

○A209.17.116.22015-11-20 → 2019-01-26 · 5 obs

○ 2015-06-19 16:16:44
● 2015-11-20 22:55:30
● 2019-01-26 15:21:56
○ 2026-09-23 22:02:12
○ 2026-09-30 22:38:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
processcontrolservices.com	ns4-34.azure-dns.info, ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org	2 records

✅ Authoritative Response

Server:13.107.222.34

NS records: ns4-34.azure-dns.info, ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for processcontrolservices.com (unsigned zone)

⏱️ Timing

Total: 1495ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`151.101.1.124, 151.101.129.124...`
NS	4	`ns1-34.azure-dns.com, ns2-34.azure-dns.net...`
MX	2	`us-smtp-inbound-1.mimecast.com (pri: 10), us-smtp-inbound-2.mimecast.com (pri: 10)`
TXT	1	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}.`
SOA	1	`ns1-34.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-34.azure-dns.com, ns1-34.azure-dns.com)

Analysis

IP Addresses

processcontrolservices.com directs to four IP numbers, which are 151.101.1.124, 151.101.65.124, 151.101.129.124 and 151.101.193.124.

Two other host names, along with casa-chic.com, lexon-design.com and knobdeals.com, also share IP numbers with processcontrolservices.com.

Name Servers

The NS records for processcontrolservices.com point to four name servers: ns1-34.azure-dns.com, ns4-34.azure-dns.info, ns2-34.azure-dns.net and ns3-34.azure-dns.org.

At least some of processcontrolservices.com's name servers are shared with other domains, for example interlinkutilities.com, hetrotter.co.uk, karimestate.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-34.azure-dns.com directs to 150.171.10.34 and 2603:1061:0:10::22; ns4-34.azure-dns.info directs to 13.107.206.34 and 2620:1ec:bda:10::22; ns2-34.azure-dns.net directs to 150.171.16.34 and 2620:1ec:8ec:10::22; ns3-34.azure-dns.org directs to 13.107.222.34 and 2a01:111:4000:10::22.

Mail Servers

processcontrolservices.com is served by two mail servers, us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com.

Among the domains sharing a mail server setup with processcontrolservices.com are gaminganalytics.ai, mesmglobal.com, tapestrystation.com and two others.

There is at least a partial MX overlap between processcontrolservices.com and other domains, including nsttransport.com, epminerals.com, iobiholdings.com and two others.

DNS names with 6 IP addresses:

us-smtp-inbound-1.mimecast.com resolves to 170.10.128.141, 170.10.128.221 and 170.10.128.242 among others, with 3 other IP addresses in total.

us-smtp-inbound-2.mimecast.com resolves to 170.10.128.141, 170.10.128.221 and 170.10.128.242 among others, with 3 other IP addresses in total.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.128.141 IP addresses.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.128.221 IP addresses.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.128.242 IP addresses.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.132.141 IP addresses.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.132.221 IP addresses.

us-smtp-inbound-1.mimecast.com along with us-smtp-inbound-2.mimecast.com each resolve to 170.10.132.242 IP addresses.