`servicesmailsignal.pro`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::ac43:8f85^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:578c^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.87.140^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.143.133^{🇺🇸 Cloudflare172.67.128.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::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		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:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.111.26^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f26.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
TXT	`google-site-verification=xT9uLLCT7iFB0vJd_T-7REUUEldzeWZgnc-qMvuXmiw`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.87.140, 172.67.143.133
		IPv6 hints	2606:4700:3035::ac43:8f85, 2606:4700:3037::6815:578c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=99, name=cloudflare-ech.com
SOA	`journey.ns.cloudflare.com`dns@cloudflare.com serial=2408328754

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

⚠️ On DNS blocklist: tif

Same first word

servicesmailsignal.pro

DNS History

7 records (7 active, 0 former)

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

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

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

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

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

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

●A104.21.87.1402026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

●A172.67.143.1332026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

●A2606:4700:3035::ac43:8f852026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

●A2606:4700:3037::6815:578c2026-07-27 → 2026-07-29 · 2 obs

● 2026-07-27 16:55:58
● 2026-07-29 07:15:04

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:108.162.193.135

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for servicesmailsignal.pro (unsigned zone)

⏱️ Timing

Total: 783ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.87.140, 172.67.143.133`
AAAA	2	`2606:4700:3035::ac43:8f85, 2606:4700:3037::6815:578c`
NS	2	`journey.ns.cloudflare.com, paul.ns.cloudflare.com`
MX	1	`smtp.google.com (pri: 1)`
TXT	2	`google-site-verification=xT9uLLCT7iFB0vJ, 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

servicesmailsignal.pro directs to four IP numbers, which are 104.21.87.140, 172.67.143.133, 2606:4700:3035::ac43:8f85 and 2606:4700:3037::6815:578c.

aquariuslandscaping.com, mail.theonethatgotaway.com.au, umwkonawetengah.ac.id and two other host names share IP numbers with servicesmailsignal.pro.

Name Servers

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

servicesmailsignal.pro uses the same name servers as several other domains — among them servicesdeck.pro, servicessystem.pro, servicesgateway.pro and two more.

There is at least partial name server overlap between servicesmailsignal.pro and other domains — nylandermuseum.org, aphroditedirect.com, pfaa.com and two more among them.

These name servers are routinely deployed together with the name servers arya.ns.cloudflare.com.

Hostnames that resolve to 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

Mail for servicesmailsignal.pro is handled by a single mail server, smtp.google.com.

servicesmailsignal.pro uses an identical mail server configuration to several other domains — among them realestatetraininghub.com, beagleforpms.com, copperopolisfire.gov and two more.

servicesmailsignal.pro has at least partial mail server overlap with other domains such as smmproduction.com, jollyengg.com, grexa.ai and two more.

smtp.google.com resolves to 9 IP addresses — 142.251.16.26, 142.251.16.27, 142.251.111.26 and 6 others.

servicesmailsignal.pro - robtex.com