Hostname
fighter.onlyplaygames.net
Last fetched
fighter.onlyplaygames.net resolves to 18.244.146.105, announced in 18.244.146.0/23 by AMAZON-02 - Amazon.com, Inc. in PL. fighter.onlyplaygames.net 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
- 18.244.146.105
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.20
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.51
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 18.244.146.65
18.244.146.0/23 · AMAZON-02 - Amazon.com, Inc. · Warsaw, PL
- 65.9.46.56
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.61
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.79
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 65.9.46.95
65.9.46.0/24 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
IPv6 resolution
No AAAA record for fighter.onlyplaygames.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fighter.onlyplaygames.net. 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-203.awsdns-25.com
- ns-816.awsdns-38.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-1353.awsdns-41.org
- ns-1785.awsdns-31.co.uk
Threat-feed evidence
History
Related pages
Pivot from fighter.onlyplaygames.net 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: "fighter.onlyplaygames.net"})-[: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.