Skip to content

Hostname

yoriso.com

Last fetched

yoriso.com resolves to 108.138.7.126, announced in 108.138.0.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. yoriso.com 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 · yoriso.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/yoriso.com

Resolution chain

IPv6 resolution

No AAAA record for yoriso.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
minrevi co.,ltd.
Contact emails
dev-admin@yoriso.com, dev-admin@minrevi.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.

Mail and authentication

Nameservers

  • ns-302.awsdns-37.com
  • ns-720.awsdns-26.net
  • 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
  • ns-1291.awsdns-33.org
  • ns-1726.awsdns-23.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: mktomail.com
  • include: _spf.salesforce.com
  • include: shops.shopify.com
  • include: _spf.activegate-ss.jp
  • ip: 13.112.64.209
  • ip: 13.113.76.159
  • ip: 157.7.186.34
  • ip: 18.182.85.25
  • ip: 203.141.249.135
  • ip: 52.199.233.54
  • ip: 54.64.126.255

Threat-feed evidence

History

Related pages

Pivot from yoriso.com 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: "yoriso.com"})-[: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.