Skip to content

Hostname

protocol.com

Last fetched

protocol.com resolves to 52.20.84.62, announced in 52.20.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. protocol.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · protocol.comRouting diversity2.4/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.9/10canon.whisper.security/host/protocol.com

Resolution chain

IPv6 resolution

No AAAA record for protocol.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:472
Registrant organisation
domain admin
Contact emails
1jqeqr4tjkjln97qgn52bghfvn@domaindiscreet.com, 2jikhebd02gj28k7ra5n6a6mt1@domaindiscreet.com, dcrj866e8ch8t88qm6t6i0sphr@domaindiscreet.com, mpdsiteadmin@welchallyn.com, xjvnfggvl@whoisprivacyprotect.com

Subdomains

Subdomain
autodiscover.protocol.com
cpanel.protocol.com
cpcalendars.protocol.com
cpcontacts.protocol.com
mail.protocol.com
research.protocol.com
webdisk.protocol.com
www.protocol.com

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns6948153129.a2dns.com
  • ns6948153130.a2dns.com
  • ns1.atom.com
  • ns2.atom.com
  • lex.ns.cloudflare.com
  • raphaela.ns.cloudflare.com
  • ns1.simulation.com
  • ns2.simulation.com
  • ns1.wakeup.com
  • ns2.wakeup.com

MX records

  • mail.protocol.com

SPF policy

  • ip: 68.66.248.49/16
  • include: spf.a2hosting.com
  • a: protocol.com
  • mx: protocol.com
  • ip: 69.48.153.129

Threat-feed evidence

History

Related pages

Pivot from protocol.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "protocol.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.