Hostname
dy.jpdata.net
Last fetched
dy.jpdata.net resolves to 139.162.124.93, announced in 139.162.96.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in JP. dy.jpdata.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
IPv6 resolution
No AAAA record for dy.jpdata.net is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dy.jpdata.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
MX records
- dymail.jpdata.net
SPF policy
- ip: 210.141.253.0/24
- ip: 219.99.190.0/25
- ip: 111.171.204.167/32
- ip: 160.86.108.96/27
- mx: dy.jpdata.net
- include: mds-c.ko-sokumail.net
- ip: 111.171.199.225
- ip: 111.171.204.221
- ip: 111.171.206.178
- ip: 111.171.217.240
- ip: 111.171.219.162
Threat-feed evidence
History
Related pages
Pivot from dy.jpdata.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: "dy.jpdata.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.