Skip to content

Hostname

ysa.org

Last fetched

ysa.org resolves to 108.167.144.234, announced in 108.167.144.0/23 by ORACLE-BMC-31898 - Oracle Corporation in US. ysa.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 · ysa.orgRouting diversity2.4/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/ysa.org

Resolution chain

IPv6 resolution

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

Attribution

oracle

ORIGIN_AS

WHOIS identity

Registrar
iana:1154
Registrant organisation
michael minks
Contact emails
ruth@butterfly.net, communications@ysa.org, mminks@ysa.org

Subdomains

Subdomain
50by250.ysa.org
autodiscover.ysa.org
cpanel.ysa.org
cpcalendars.ysa.org
cpcontacts.ysa.org
donate.ysa.org
gysd-org.ysa.org
leadasap.ysa.org
mail.ysa.org
projects.ysa.org
servenet-org.ysa.org
webdisk.ysa.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

Mail and authentication

Nameservers

  • ns1.bluehost.com
  • ns2.bluehost.com
  • 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

  • ysa-org.mail.protection.outlook.com

SPF policy

  • include: bluehost.com
  • include: spf.protection.outlook.com
  • a: ysa.org
  • mx: ysa.org
  • ip: 108.167.144.234
  • ip: 162.241.173.234

Threat-feed evidence

History

Related pages

Pivot from ysa.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: "ysa.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.