`pfpulse.tech`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::ac43:a251^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::6815:3aae^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.58.174^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.162.81^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`may.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a87^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c087^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`may.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2087^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`may.ns.cloudflare.com`
		A	108.162.192.135^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	172.64.32.135^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
		A	173.245.58.135^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`may.ns.cloudflare.com`
NS	`theo.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b90^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`theo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c190^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`theo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2190^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`theo.ns.cloudflare.com`
		A	108.162.193.144^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`theo.ns.cloudflare.com`
		A	172.64.33.144^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`theo.ns.cloudflare.com`
		A	173.245.59.144^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`theo.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽³⁶⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁸¹⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`brevo-code:4fa69e06dc115a2a9744078dd4a862a4`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.58.174, 172.67.162.81
		IPv6 hints	2606:4700:3032::ac43:a251, 2606:4700:3033::6815:3aae
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=210, name=cloudflare-ech.com
SOA	`may.ns.cloudflare.com`dns@cloudflare.com serial=2402527858

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1778627945

Same first word

pfpulse.tech

Similar names

epfplus.com

DNS History

9 records (9 active, 0 former)

●NSmay.ns.cloudflare.com2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●NStheo.ns.cloudflare.com2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●MXroute1.mx.cloudflare.net2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●MXroute2.mx.cloudflare.net2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●MXroute3.mx.cloudflare.net2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●A104.21.58.1742026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●A172.67.162.812026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●A2606:4700:3032::ac43:a2512026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

●A2606:4700:3033::6815:3aae2026-05-12 → 2026-05-12 · 2 obs

● 2026-05-12 04:16:32
● 2026-05-12 23:31:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
pfpulse.tech	may.ns.cloudflare.com, theo.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.58.135

NS records: may.ns.cloudflare.com, theo.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pfpulse.tech (unsigned zone)

⏱️ Timing

Total: 507ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.58.174, 172.67.162.81`
AAAA	2	`2606:4700:3033::6815:3aae, 2606:4700:3032::ac43:a251`
NS	2	`may.ns.cloudflare.com, theo.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 17), route3.mx.cloudflare.net (pri: 36)...`
TXT	2	`brevo-code:4fa69e06dc115a2a9744078dd4a86, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`may.ns.cloudflare.com dns.cloudflare.com`

Analysis

IP Addresses

pfpulse.tech resolves to four IP numbers: 2606:4700:3032::ac43:a251, 2606:4700:3033::6815:3aae, 104.21.58.174 and 172.67.162.81.

other host names for instance leadingpointmarketing.com, makekowupuainvestments.click, mogtoken.net, noventhorvia.com and zotost.com share IP numbers with pfpulse.tech.

Name Servers

pfpulse.tech is delegated to two name servers: may.ns.cloudflare.com and theo.ns.cloudflare.com.

pfpulse.tech shares the same name server setup as other domains, for example bebga.com, techpoint.com.tr, landroverforum.com, k-net.org and hdtruckforum.com.

pfpulse.tech at least partially shares name servers with other domains, for instance happytool.com, mayafellernutrition.com, iawesome.com, silvaronethq.sbs and hy688.com.

These name servers are commonly used with gwen.ns.cloudflare.com, galilea.ns.cloudflare.com, meiling.ns.cloudflare.com and chan.ns.cloudflare.com.

Host names with six IP numbers:

may.ns.cloudflare.com points to: 2606:4700:50::adf5:3a87, 2803:f800:50::6ca2:c087, 2a06:98c1:50::ac40:2087, 108.162.192.135, 172.64.32.135 and 173.245.58.135; theo.ns.cloudflare.com points to: 2606:4700:58::adf5:3b90, 2803:f800:50::6ca2:c190, 2a06:98c1:50::ac40:2190, 108.162.193.144, 172.64.33.144 and 173.245.59.144.

Mail Servers

pfpulse.tech is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

pfpulse.tech shares mail servers with other domains at least partially, including menddez.com, drugrehabwestminster.com, comexim-adexim.com.br, nabative.com and myrecipia.com.

Host names with six IP numbers: route1.mx.cloudflare.net points to: 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13; route2.mx.cloudflare.net points to: 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19; route3.mx.cloudflare.net points to: 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

pfpulse.tech - robtex.com

pfpulse.tech

tech

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`pfpulse.tech`

`tech`