Skip to content

Hostname

numo.or.jp

Last fetched

numo.or.jp resolves to 13.113.60.90, announced in 13.112.0.0/14 by AMAZON-02 - Amazon.com, Inc. in JP. numo.or.jp 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 · numo.or.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/numo.or.jp

Resolution chain

IPv6 resolution

No AAAA record for numo.or.jp is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
nuclear waste management organization of japan

Subdomains

Subdomain
cms.numo.or.jp
contest2023.numo.or.jp
dev.numo.or.jp
qadb.numo.or.jp
scct.numo.or.jp
stg.numo.or.jp
www.numo.or.jp

Showing 7 of 7 subdomains (7 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

Sample outbound links

Mail and authentication

Nameservers

  • skydns11.otsuka-office365.jp
  • skydns12.otsuka-office365.jp
  • skydns13.otsuka-office365.jp
  • skydns99.otsuka-office365.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

  • numo-or-jp.mail.protection.outlook.com

SPF policy

  • ip: 157.205.29.58/32
  • include: spf.mta.hdems.com
  • include: spf.protection.outlook.com
  • include: _bcspf4n.guardianwall.jp

Threat-feed evidence

History

Related pages

Pivot from numo.or.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: "numo.or.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 20

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