🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`responsify.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::ac43:8a7d^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:40fa^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.64.250^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.138.125^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`nina.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a88^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nina.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c088^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`nina.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2088^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`nina.ns.cloudflare.com`
		A	108.162.192.136^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nina.ns.cloudflare.com`
		A	172.64.32.136^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nina.ns.cloudflare.com`
		A	173.245.58.136^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nina.ns.cloudflare.com`
NS	`peyton.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bdd^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peyton.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1dd^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`peyton.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21dd^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`peyton.ns.cloudflare.com`
		A	108.162.193.221^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peyton.ns.cloudflare.com`
		A	172.64.33.221^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peyton.ns.cloudflare.com`
		A	173.245.59.221^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`peyton.ns.cloudflare.com`
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`
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	`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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.64.250, 172.67.138.125
		IPv6 hints	2606:4700:3035::ac43:8a7d, 2606:4700:3036::6815:40fa
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=144, name=cloudflare-ech.com
SOA	`nina.ns.cloudflare.com`dns@cloudflare.com serial=2413063852

`dev`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

responsify.it

responsify.co

responsify.se

responsify.com

responsify.dev

responsify.us

responsify.app

responsify.nl

responsify.de

Similar names

pressonify.co

perssonify.com

infosyserp.com

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSnina.ns.cloudflare.com2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●NSpeyton.ns.cloudflare.com2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●MXroute1.mx.cloudflare.net2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●MXroute2.mx.cloudflare.net2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●MXroute3.mx.cloudflare.net2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●A104.21.64.2502026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●A172.67.138.1252026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●A2606:4700:3035::ac43:8a7d2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

●A2606:4700:3036::6815:40fa2026-08-27 → 2026-09-01 · 2 obs

● 2026-08-27 15:11:34
● 2026-09-01 13:13:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
responsify.dev	nina.ns.cloudflare.com, peyton.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.221

NS records: nina.ns.cloudflare.com, peyton.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 815ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.138.125, 104.21.64.250`
AAAA	2	`2606:4700:3035::ac43:8a7d, 2606:4700:3036::6815:40fa`
NS	2	`nina.ns.cloudflare.com, peyton.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 2), route3.mx.cloudflare.net (pri: 21)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`nina.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

responsify.dev resolves to four IP addresses: 104.21.64.250, 172.67.138.125, 2606:4700:3035::ac43:8a7d and 2606:4700:3036::6815:40fa.

Two other host names, along with kinopersik.net, ewotiko.top and geniegaragedooropenerservices.com, also share IP numbers with responsify.dev.

Name Servers

responsify.dev is delegated to two name servers: nina.ns.cloudflare.com and peyton.ns.cloudflare.com.

responsify.dev shares its NS records with other domains, for example saiddcruz.com, clinicasyl.com, canvasprints.com and two others.

responsify.dev partially shares its NS delegation with several other domains, including ygj56.workers.dev, talktochatgpt.xyz, ahocir0.cn and two others.

The name servers olivia.ns.cloudflare.com, ignat.ns.cloudflare.com, adrian.ns.cloudflare.com and thomas.ns.cloudflare.com are often found in use alongside these name servers.

DNS names with 6 IP addresses:

nina.ns.cloudflare.com resolves to 108.162.192.136, 172.64.32.136, 173.245.58.136 and 3 other IP addresses.

peyton.ns.cloudflare.com resolves to 108.162.193.221, 172.64.33.221, 173.245.59.221 and 3 other IP addresses.

Mail Servers

responsify.dev uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

There is at least a partial MX overlap between responsify.dev and other domains, including pertanianumwbuton.ac.id, lifengaged.com, tba4.gr and two others.

DNS names with 6 IP addresses:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.

responsify.dev - robtex.com

responsify.dev

dev

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`responsify.dev`

`dev`