Skip to content

Hostname

genrage.com

Last fetched

genrage.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. genrage.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Tue, 22 Sep 2026 19:47:37 GMT

Nutrition Label

WHISPER CANON · genrage.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/genrage.com

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
account.genrage.com
www.genrage.com

Showing 2 of 2 subdomains (2 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

  • ns19.domaincontrol.com
  • ns20.domaincontrol.com
  • 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

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

Threat-feed evidence

History

Related pages

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