Skip to content

Hostname

ypl.org

Last fetched

ypl.org is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. ypl.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 · ypl.orgRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/ypl.org

Resolution chain

No IPv4 resolution is recorded for ypl.org in WhisperGraph.

IPv6 resolution

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
k94q84v59zc@networksolutionsprivateregistration.com, ry2p35hu7mm@networksolutionsprivateregistration.com, tm4vd5c34ut@networksolutionsprivateregistration.com, v945y73c7m6@networksolutionsprivateregistration.com, xh8ya5qf6j7@networksolutionsprivateregistration.com

Subdomains

Subdomain
applications.ypl.org
archive.ypl.org
csg.ypl.org
kaseya.ypl.org
mail.ypl.org
mobileprint.ypl.org
smtp.ypl.org
webmail.ypl.org
work.ypl.org
www.ypl.org

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

  • ns1198.dns.dyn.com
  • ns2136.dns.dyn.com
  • ns3175.dns.dyn.com
  • ns4129.dns.dyn.com
  • ns1.mydyndns.org

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: _spf.psm.knowbe4.com
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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