Hostname
yamapy.net
Last fetched
yamapy.net resolves to 183.90.242.33, announced in 183.91.69.0/24 by XSERVER - Xserver Inc. in JP. yamapy.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 yamapy.net is recorded in WhisperGraph.
Attribution
xserver
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
Subdomains
| Subdomain |
|---|
| mta-sts.yamapy.net |
| www.yamapy.net |
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns1.xserver.jp
- ns2.xserver.jp
- ns3.xserver.jp
- ns4.xserver.jp
- ns5.xserver.jp
MX records
- yamapy.net
SPF policy
- include: spf.sender.xserver.jp
- a: sv2132.xserver.jp
- a: yamapy.net
- mx: yamapy.net
Threat-feed evidence
History
Related pages
Pivot from yamapy.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: "yamapy.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.