Skip to content

Hostname

peergame.com

Last fetched

peergame.com resolves to 13.227.249.120, announced in 13.227.249.0/24 by AMAZON-02 - Amazon.com, Inc. in IN. peergame.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 · peergame.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/peergame.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:447
Registrant organisation
elewechi okike
Contact emails
enmokike@hotmail.com, 9e224d14d809494994807de03f914cfb.protect@withheldforprivacy.com, d904ed6c4f604e34892b25d8913a6a8d.protect@withheldforprivacy.com, support@namecheap.com, aqwueakwnlaw@idp.email

Subdomains

Subdomain
blog.peergame.com
community.peergame.com
dev.peergame.com
help.peergame.com
promotions.peergame.com
staging.peergame.com
www.peergame.com

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

  • ns-53.awsdns-06.com
  • ns-561.awsdns-06.net
  • ns-1253.awsdns-28.org
  • ns-1822.awsdns-35.co.uk

MX records

  • feedback-smtp.ap-northeast-1.amazonses.com
  • 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: amazonses.com
  • include: ap-northeast-1.amazonses.com
  • include: _spf.google.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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