Hostname
dev.mrmax.jp
Last fetched
dev.mrmax.jp resolves to 108.159.227.37, announced in 108.159.224.0/21 by AMAZON-02 - Amazon.com, Inc. in US. dev.mrmax.jp 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
- 108.159.227.37
108.159.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.159.227.61
108.159.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.159.227.62
108.159.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.159.227.75
108.159.224.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.161.82.101
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.19
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.29
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.50
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for dev.mrmax.jp is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dev.mrmax.jp. 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-465.awsdns-58.com
- ns-977.awsdns-58.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-1492.awsdns-58.org
- ns-1873.awsdns-42.co.uk
MX records
- inbound-smtp.us-east-1.amazonaws.com
Threat-feed evidence
History
Related pages
Pivot from dev.mrmax.jp 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.mrmax.jp"})-[: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.