Skip to content

Hostname

frontend.consent.direct

Last fetched

frontend.consent.direct resolves to 18.158.98.81, announced in 18.156.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. frontend.consent.direct 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 · frontend.consent.directRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/frontend.consent.direct

Resolution chain

IPv6 resolution

No AAAA record for frontend.consent.direct is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for frontend.consent.direct. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • ns-142.awsdns-17.com
  • ns-738.awsdns-28.net
  • ns-1160.awsdns-17.org
  • ns-1995.awsdns-57.co.uk

Threat-feed evidence

History

Related pages

Pivot from frontend.consent.direct 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: "frontend.consent.direct"})-[: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.