fksa.org security report

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

89risk

Critical

Exposed services or known CVEs need attention now.

1Critical

3High

5Medium

4Low

2Info

Collected 18 hours ago13.7sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture2
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis15

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

Shodan matched these CVEs against the service banners it saw on 134.209.69.164 (fksa.org), which advertise vbulletin 3.8.11, openssh 9.2p1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2023-39777 CVE-2019-17271 CVE-2019-17132 CVE-2019-17131 CVE-2019-17130 CVE-2018-6200 CVE-2017-7569 CVE-2014-9463 CVE-2014-2022 CVE-2014-2021 CVE-2011-5251 CVE-2010-1077
What to do
Confirm the running versions on 134.209.69.164 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2023-39777 ↗CVE-2019-17271 ↗CVE-2019-17132 ↗CVE-2019-17131 ↗CVE-2019-17130 ↗
asset: 134.209.69.164
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 134.209.69.164:3306
Nothing tells receiving mail servers which hosts may send as @fksa.org, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: fksa.org
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.fksa.org TXT "v=DMARC1; p=none; rua=mailto:dmarc@fksa.org"`, review the reports, then move to p=quarantine and p=reject.
asset: fksa.org
134.209.69.164 (fksa.org) reports vbulletin 3.8.11, openssh 9.2p1. 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: 134.209.69.164
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: 134.209.69.164:22
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://fksa.org/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://fksa.org/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://fksa.org/
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://fksa.org/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://fksa.org/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://fksa.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: fksa.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: fksa.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: fksa.org

final https://fksa.org/status 200time 1004msstack cloudflare · vBulletin 3.8.11

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000, max-age=31536000
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie X_CACHE_KEY
no Secure · no HttpOnly · no SameSite

✓Receives mail via 2 servers
mx00.1and1.com mx01.1and1.com
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns29.1and1.com ns30.1and1.com

✓Registered with GoDaddy.com, LLC24.6 years old
fksa.org
✓Registration expiry867 days
2029-01-21
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns29.1and1.com ns30.1and1.com

Address	Ports	CVEs	Edge	Network
134.209.69.164 fksa.org +1	22804433306	12	direct	—

Archived URLs

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

fksa.org security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames