Hostname
renet.jp
Last fetched
renet.jp resolves to 150.230.208.117, announced in 150.230.192.0/19 by ORACLE-BMC-31898 - Oracle Corporation in JP. renet.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
IPv6 resolution
No AAAA record for renet.jp is recorded in WhisperGraph.
Attribution
oracle
ORIGIN_AS
WHOIS identity
- Registrant organisation
- (not displayed by registrant's request)
- Contact emails
- proxy@whoisprotectservice.com, hideaki.joko@netoff.co.jp
Subdomains
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
- 01.dnsv.jp
- 02.dnsv.jp
- 03.dnsv.jp
- 04.dnsv.jp
- 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
MX records
- renet-jp.mail.protection.outlook.com
- mx.mail.ctc.jp
- mail01.renet.jp
- mail02.renet.jp
- mail03.renet.jp
- mail11.renet.jp
SPF policy
- ip: 218.216.178.7/32
- ip: 218.216.178.8/32
- include: _spf.google.com
- include: spf.protection.outlook.com
- mx: renet.jp
- include: spf.tricorn.net
- ip: 202.124.213.131
- ip: 202.124.213.132
- ip: 202.124.213.137
Threat-feed evidence
History
Related pages
Pivot from renet.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: "renet.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.