Skip to content

Hostname

clerkretail.com

Last fetched

clerkretail.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. clerkretail.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 · clerkretail.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/clerkretail.com

Resolution chain

No IPv4 resolution is recorded for clerkretail.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of clerkretail.com owner
Contact emails
68e25906-53ed-4e46-9a73-b3202c8d723d@identity-protect.org, 6dcc3214-eb32-4346-915a-36427f868091@identity-protect.org, 75becb36-03bb-48fe-a695-d1bb91b3fa12@identity-protect.org, 8aa9e13d-37f0-4dcb-99c5-b7f3f2eafe74@identity-protect.org, b6ac53dc-dad5-4ac4-b6e0-8fad3250c575@identity-protect.org, be2c1b3a-6c5e-4bbb-82dd-724e0b98269c@identity-protect.org, owner-10195838@clerkretail.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ns-33.awsdns-04.com
  • kenneth.ns.cloudflare.com
  • mariah.ns.cloudflare.com
  • ns-771.awsdns-32.net
  • ns-1108.awsdns-10.org
  • ns-1867.awsdns-41.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: sendgrid.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

Pivot from clerkretail.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: "clerkretail.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.