ahrp.org security report

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

33risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

3Low

2Info

Collected 19 hours ago3.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs11
Registration
DNS posture3
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 404). 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.

Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 83.228.219.252:22
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://ahrp.org/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: ahrp.org
83.228.219.252 (ahrp.org) reports openssh 9.6p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 83.228.219.252
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 83.228.219.252:25
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: ahrp.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: ahrp.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: ahrp.org

final https://ahrp.org/status 200time 1150msstack cloudflare · WordPress 7.1

✓http:// redirects to https://
✗Strict-Transport-Security
✓Content-Security-Policy
default-src 'self' http: https: ws: wss: data: blob: 'unsafe-inline' 'unsafe-eval'; frame-ancestors 'self';
✓Clickjacking protection
via CSP frame-ancestors
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
✓Permissions-Policy
interest-cohort=()
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 2 servers
fb.mail.gandi.net spool.mail.gandi.net
✓SPFends in -all
v=spf1 a mx ip4:195.15.215.12 ip4:185.26.126.50 include:_mailcust.gandi.net -all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns-139-c.gandi.net ns-25-b.gandi.net ns-66-a.gandi.net

✓Registered with Gandi SAS24.0 years old
ahrp.org
✓Registration expiry728 days
2028-09-04
✓Transfer lock
client transfer prohibited
✓3 nameservers at registry
ns-139-c.gandi.net ns-25-b.gandi.net ns-66-a.gandi.net

Address	Ports	CVEs	Edge	Network
83.228.219.252 ahrp.org +1	22258081143443465587+3	0	direct	—

Archived URLs

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

ahrp.org security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames