Hostname
dev1.mrmax.jp
Last fetched
dev1.mrmax.jp resolves to 108.157.32.112, announced in 108.157.32.0/21 by AMAZON-02 - Amazon.com, Inc. in SG. dev1.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.157.32.112
108.157.32.0/21 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 108.157.32.119
108.157.32.0/21 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 108.157.32.29
108.157.32.0/21 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 108.157.32.47
108.157.32.0/21 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.170.51.124
3.170.51.0/24 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.170.51.26
3.170.51.0/24 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.170.51.34
3.170.51.0/24 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.170.51.41
3.170.51.0/24 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
IPv6 resolution
No AAAA record for dev1.mrmax.jp is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dev1.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-204.awsdns-25.com
- ns-639.awsdns-15.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-1149.awsdns-15.org
- ns-1947.awsdns-51.co.uk
MX records
- inbound-smtp.us-west-2.amazonaws.com
Threat-feed evidence
History
Related pages
Pivot from dev1.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: "dev1.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.