Hostname
dev.peergame.com
Last fetched
dev.peergame.com resolves to 13.225.117.107, announced in 13.225.117.0/24 by AMAZON-02 - Amazon.com, Inc. in KR. dev.peergame.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.225.117.107
13.225.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 13.225.117.111
13.225.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 13.225.117.125
13.225.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 13.225.117.36
13.225.117.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.169.252.10
3.169.252.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.252.105
3.169.252.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.252.127
3.169.252.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.169.252.94
3.169.252.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for dev.peergame.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dev.peergame.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-223.awsdns-27.com
- ns-914.awsdns-50.net
- ns-1099.awsdns-09.org
- ns-1681.awsdns-18.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 dev.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: "dev.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.