Skip to content

Hostname

fugogames.com

Last fetched

fugogames.com resolves to 13.49.194.166, announced in 13.48.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SE. fugogames.com 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 · fugogames.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/fugogames.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of fugogames.com owner
Contact emails
7ad89457-b171-41d9-a665-fe0a8d53b656@identity-protect.org, 7cfab4a8-16ea-443e-a375-3b8c014e53bb@identity-protect.org, 8d70940b-b158-428a-92ad-b9791a1a70dc@identity-protect.org, 9268b40c-7ca4-4bfd-9141-b9966ac8f392@identity-protect.org, a555cc3c-3ddd-4d24-bc07-8acbd1ec9ca0@identity-protect.org, f6fb2298-7bc6-4626-83ec-aef756b766ba@identity-protect.org, owner-9236612@fugogames.com.whoisprivacyservice.org

Subdomains

Subdomain
wordmasterresources.fugogames.com
wowcoopevent.fugogames.com
wowzenresources.fugogames.com

Showing 3 of 4. View all subdomains →

Mail and authentication

Nameservers

  • ns-320.awsdns-40.com
  • ns-732.awsdns-27.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-1454.awsdns-53.org
  • ns-1953.awsdns-52.co.uk

MX records

  • mx.yandex.net

SPF policy

  • redirect: _spf.yandex.net

Threat-feed evidence

History

Related pages

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