Skip to content

Hostname

fancygamestudio.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of fancygamestudio.com owner
Contact emails
012ca6ea-0cfe-497a-b684-278c73d82399@identity-protect.org, 3ffb9a3d-9408-4531-ad7c-f18e719a415f@identity-protect.org, b8cff96d-3c1b-4def-aba4-4201613097b2@identity-protect.org, cfd70afa-6d2b-4d8b-ba51-5ffce48da515@identity-protect.org

Subdomains

Subdomain
gs-api.fancygamestudio.com
ta.fancygamestudio.com

Showing 2 of 4. View all subdomains →

Mail and authentication

Nameservers

  • ns-346.awsdns-43.com
  • ns-756.awsdns-30.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-1102.awsdns-09.org
  • ns-1649.awsdns-14.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

Threat-feed evidence

History

Related pages

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