Skip to content

Hostname

hyper.wtf

Last fetched

hyper.wtf resolves to 194.87.68.232, announced in 194.87.68.0/23 by ASBAXET - LLC Baxet in RU. hyper.wtf 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 · hyper.wtfRouting diversity2.4/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/hyper.wtf

Resolution chain

IPv6 resolution

Attribution

baxet

ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domains by proxy,
Contact emails
hyper.wtf@domainsbyproxy.com, pw-452815a6983bb0a354db938344d7f354@privacyguardian.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

  • 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
  • brb.hyper.wtf
  • idk.hyper.wtf
  • ilu.hyper.wtf

MX records

  • hyperre.al

SPF policy

  • include: spf.hyperre.al

Threat-feed evidence

History

Related pages

Pivot from hyper.wtf 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: "hyper.wtf"})-[: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.