Skip to content

Hostname

freerobux.com

Last fetched

freerobux.com resolves to 13.248.128.132, announced in 13.248.128.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. freerobux.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:35 GMT
Last seen on a feed
Tue, 15 Sep 2026 00:18:35 GMT

Nutrition Label

WHISPER CANON · freerobux.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/freerobux.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domain admin
Contact emails
contact@privacyprotect.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-318.awsdns-39.com
  • ns-888.awsdns-47.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-1111.awsdns-10.org
  • ns-1762.awsdns-28.co.uk

MX records

  • egay2gnuznrsviz7ywhs7nb3k5xn4dc3hav6eudrd6labkds266q.mx-verification.google.com
  • smtp.google.com

Threat-feed evidence

History

Related pages

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