Skip to content

Hostname

wavebrowserbase.com

Last fetched

wavebrowserbase.com resolves to 100.27.53.148, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. wavebrowserbase.com is listed by 1 threat feed; reconciled level MEDIUM.

Threat posture

24threat score (procedure-native scale)

MEDIUM

Listed by 1 threat feed. Advisory: popularity-trust-offset.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:51:25 GMT
Last seen on a feed
Sun, 13 Sep 2026 00:52:18 GMT

Nutrition Label

WHISPER CANON · wavebrowserbase.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/wavebrowserbase.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
23398eee-f0cb-4575-85c7-c160db20250d@identity-protect.org, 40231644-aba3-42bc-abef-9ba63477404e@identity-protect.org, 9f2ee859-650c-4106-be05-0d0642d3b394@identity-protect.org, bb03b940-a06b-4719-8d8d-037acced89e6@identity-protect.org, c8c7aee2-b360-4b8d-893b-9cdca690945f@identity-protect.org, d37e95a0-a8f6-4f52-90b9-e6f334b05a04@identity-protect.org, owner-497986@wavebrowserbase.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-170.awsdns-21.com
  • ns-923.awsdns-51.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1337.awsdns-39.org
  • ns-1877.awsdns-42.co.uk

Threat-feed evidence

History

Related pages

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