Skip to content

Hostname

rogiken.org

Last fetched

rogiken.org resolves to 160.16.136.121, announced in 160.16.128.0/17 by SAKURA-B - SAKURA Internet Inc. in JP. rogiken.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · rogiken.orgRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/rogiken.org

Resolution chain

IPv6 resolution

No AAAA record for rogiken.org is recorded in WhisperGraph.

Attribution

sakura

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
societyforthe study of robotics
Contact emails
kueno@rogiken.org

Subdomains

Subdomain
blog.rogiken.org
crossposter.rogiken.org
doc.rogiken.org
equipment.rogiken.org
git.rogiken.org
jenkins.rogiken.org
maquinista.rogiken.org
maquiwiki.rogiken.org
mastodon.rogiken.org
nextcloud.rogiken.org
owncloud.rogiken.org
poifull.rogiken.org

Showing 12 of 17. View all 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

Sample outbound 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

  • rogiken.org

SPF policy

  • mx: rogiken.org

Threat-feed evidence

History

Related pages

Pivot from rogiken.org 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: "rogiken.org"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.