yerf.org security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

48risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

3Medium

1Low

2Info

Collected 14 hours ago4.5sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis7

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.yerf.org TXT "v=DMARC1; p=none; rua=mailto:dmarc@yerf.org"`, review the reports, then move to p=quarantine and p=reject.
asset: yerf.org
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://yerf.org/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://yerf.org/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: yerf.org
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: yerf.org
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: yerf.org
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: yerf.org

final https://yerf.org/status 200time 692msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
same-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
yerf-org.mail.protection.outlook.com
!SPFends in ~all
v=spf1 include:spf.easyname.com include:spf.protection.outlook.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
marjory.ns.cloudflare.com paul.ns.cloudflare.com

✓Registered with Ascio Technologies, Inc. Danmark - Filial af Ascio technologies, Inc. USA8.6 years old
yerf.org
✓Registration expiry147 days
2027-02-01
✗Transfer lock
none
✓2 nameservers at registry
marjory.ns.cloudflare.com paul.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.21.66.205 yerf.org	80443205220532082208320862087+5	0	Cloudflare~	—
172.67.207.64 yerf.org +1	80443205220532082208320862087+5	0	Cloudflare~	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

yerf.org security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames