🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`protocolapp.net`

DNSSEC	⚠️ Not signed
A	138.201.200.41^{🇩🇪 Hetzner138.201.0.0/16 HETZNER-RZ-BLK-ERX4}
		PTR	`static.41.200.201.138.clients.your-server.de`
NS	`cortney.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a57^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cortney.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c057^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`cortney.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2057^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`cortney.ns.cloudflare.com`
		A	108.162.192.87^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cortney.ns.cloudflare.com`
		A	172.64.32.87^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cortney.ns.cloudflare.com`
		A	173.245.58.87^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cortney.ns.cloudflare.com`
NS	`rick.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b8b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c18b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rick.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:218b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rick.ns.cloudflare.com`
		A	108.162.193.139^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	172.64.33.139^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	173.245.59.139^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.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	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`cortney.ns.cloudflare.com`dns@cloudflare.com serial=2418502648

`net`

	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=1793213221

Same first word

protocolapp.app

protocolapp.uk

protocolapp.health

protocolapp.fyi

protocolapp.ai

protocolapp.com

protocolapp.io

protocolapp.net

protocolapp.cc

protocolapp.org

Similar names

appprotocol.nl

appprotocol.com

papprotocol.org

appprotocol.xyz

Previous names

Next names

DNS History

6 records (6 active, 0 former)

●NScortney.ns.cloudflare.com2026-08-26 → 2026-10-28 · 2 obs

● 2026-08-26 22:47:04
● 2026-10-28 19:04:10

●NSrick.ns.cloudflare.com2026-08-26 → 2026-10-28 · 2 obs

● 2026-08-26 22:47:04
● 2026-10-28 19:04:10

●MXroute1.mx.cloudflare.net2026-10-23 → 2026-10-28 · 2 obs

● 2026-10-23 19:11:40
● 2026-10-28 19:04:10

●MXroute2.mx.cloudflare.net2026-10-23 → 2026-10-28 · 2 obs

● 2026-10-23 19:11:40
● 2026-10-28 19:04:10

●MXroute3.mx.cloudflare.net2026-10-23 → 2026-10-28 · 2 obs

● 2026-10-23 19:11:40
● 2026-10-28 19:04:10

●A138.201.200.412026-08-26 → 2026-10-28 · 2 obs

● 2026-08-26 22:47:04
● 2026-10-28 19:04:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	b.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net...	-
protocolapp.net	rick.ns.cloudflare.com, cortney.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.192.87

NS records: rick.ns.cloudflare.com, cortney.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for protocolapp.net (unsigned zone)

⏱️ Timing

Total: 616ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`138.201.200.41`
NS	2	`cortney.ns.cloudflare.com, rick.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 1), route3.mx.cloudflare.net (pri: 29)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`cortney.ns.cloudflare.com dns.cloudflare`

Analysis

IP Addresses

protocolapp.net resolves to one IP address: 138.201.200.41.

There are other host names — barcelonainternationalsocial.com among them — that share IP numbers with protocolapp.net.

Name Servers

DNS delegation for protocolapp.net points to two name servers: cortney.ns.cloudflare.com and rick.ns.cloudflare.com.

protocolapp.net uses the same name servers as several other domains — among them ruppisresort.com, imsafetoday.com, wilsonwings.com and two more.

protocolapp.net has at least partial name server overlap with other domains, such as raploy.com, bgeneralx.store, personal-website-dty.pages.dev and two others.

It is common to see these name servers used together with name servers simon.ns.cloudflare.com and kate.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

cortney.ns.cloudflare.com has IP addresses 108.162.192.87, 172.64.32.87 and 173.245.58.87, plus 3 other.

rick.ns.cloudflare.com has IP addresses 108.162.193.139, 172.64.33.139 and 173.245.59.139, plus 3 other.