`servicescontrol.pro`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:a533^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:59d9^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.89.217^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.165.51^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`journey.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2603^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c203^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`journey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2203^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`journey.ns.cloudflare.com`
		A	108.162.194.3^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	162.159.38.3^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
		A	172.64.34.3^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`journey.ns.cloudflare.com`
NS	`paul.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b87^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paul.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c187^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`paul.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2187^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`paul.ns.cloudflare.com`
		A	108.162.193.135^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paul.ns.cloudflare.com`
		A	172.64.33.135^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paul.ns.cloudflare.com`
		A	173.245.59.135^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paul.ns.cloudflare.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	2607:f8b0:4004:c19::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
TXT	`google-site-verification=yCOQO1efM1P1BZeqz1tZOJmCx-aEGxb7sduhStPXvU8`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.89.217, 172.67.165.51
		IPv6 hints	2606:4700:3031::ac43:a533, 2606:4700:3036::6815:59d9
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=232, name=cloudflare-ech.com
SOA	`journey.ns.cloudflare.com`dns@cloudflare.com serial=2408326615

`pro`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.pro.afilias-nst.info` ⭐
	NS	`a2.pro.afilias-nst.info`
	NS	`b0.pro.afilias-nst.org`
	NS	`b2.pro.afilias-nst.org`
	NS	`c0.pro.afilias-nst.info`
	NS	`d0.pro.afilias-nst.org`
	SOA	`a0.pro.afilias-nst.info`hostmaster@donuts.email serial=1785193991

⚠️ On DNS blocklist: tif

Same first word

servicescontrol.pro

Similar names

controlservices.com.br

controlservices.biz

controlservices.com

controlservices.co.nz

controlservices.it

servicecontrols.com

DNS History

7 records (7 active, 0 former)

●NSjourney.ns.cloudflare.com2026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●NSpaul.ns.cloudflare.com2026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●MXsmtp.google.com2026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●A104.21.89.2172026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●A172.67.165.512026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●A2606:4700:3031::ac43:a5332026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

●A2606:4700:3036::6815:59d92026-07-26 → 2026-07-27 · 2 obs

● 2026-07-26 01:54:02
● 2026-07-27 23:18:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pro	b0.pro.afilias-nst.org, b2.pro.afilias-nst.org, c0.pro.afilias-nst.info, d0.pro.afilias-nst.org...	-
servicescontrol.pro	journey.ns.cloudflare.com, paul.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.135

NS records: journey.ns.cloudflare.com, paul.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for servicescontrol.pro (unsigned zone)

⏱️ Timing

Total: 565ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.165.51, 104.21.89.217`
AAAA	2	`2606:4700:3036::6815:59d9, 2606:4700:3031::ac43:a533`
NS	2	`journey.ns.cloudflare.com, paul.ns.cloudflare.com`
MX	1	`smtp.google.com (pri: 1)`
TXT	2	`google-site-verification=yCOQO1efM1P1BZe, v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`journey.ns.cloudflare.com dns.cloudflare`

Analysis

IP Addresses

servicescontrol.pro directs to four IP numbers, which are 104.21.89.217, 172.67.165.51, 2606:4700:3031::ac43:a533 and 2606:4700:3036::6815:59d9.

Two other host names, along with bkjucmhe5.sljbj.com, xlrir6e6ku.wz8em76uq8.sljbj.com and 4qvnm1bij2.sljbj.com, also share IP numbers with servicescontrol.pro.

Name Servers

Two name servers handle the delegation for servicescontrol.pro: journey.ns.cloudflare.com and paul.ns.cloudflare.com.

servicescontrol.pro shares its NS records with other domains, for example servicescenter.pro, servicesworks.pro, servicesmission.pro and two others.

At least some of servicescontrol.pro's name servers are shared with other domains, for example tristartechsolutions.co.uk, adconnectbrazil.com, northhillnursingandrehab.com and two more.

These name servers tend to be used in conjunction with the name servers arya.ns.cloudflare.com.

DNS names with 6 IP addresses:

journey.ns.cloudflare.com resolves to 108.162.194.3, 162.159.38.3 and 172.64.34.3 among others, with 3 other IP addresses in total.

paul.ns.cloudflare.com resolves to 108.162.193.135, 172.64.33.135 and 173.245.59.135 among others, with 3 other IP addresses in total.

Mail Servers

The sole mail server for servicescontrol.pro is smtp.google.com.

Among the domains sharing a mail server setup with servicescontrol.pro are csaxa.com, brasildasorte.bet.br, sfpquantiv.com and two others.

There is at least a partial MX overlap between servicescontrol.pro and other domains, including wearedorothy.com, failed.biz, letsruck.com and two others.

These mail servers frequently co-occur with the mail servers aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

With 9 IP addresses total, smtp.google.com resolves to 142.251.16.27, 142.251.111.27, 172.253.63.26 and 6 others.

servicescontrol.pro - robtex.com