mofga.org security report

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

75risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

4Medium

2Low

1Info

Collected 10 hours ago7.4sfrom cache

Certificate Transparency13
DNS resolution14
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs46
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis9

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.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 149.210.171.6 (pumphouse.mofga.org), which advertise openssh 5.3. 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-2026-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2023-51767 CVE-2023-51385 CVE-2023-48795 ...and 33 more
What to do
Confirm the running versions on 149.210.171.6 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 149.210.171.6
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 149.210.171.6:3306
149.210.171.6 (pumphouse.mofga.org) reports openssh 5.3. 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: 149.210.171.6
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 149.210.171.6:21
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: 149.210.171.6: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://www.mofga.org/
vpn.mofga.org appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: vpn.mofga.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: mofga.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: mofga.org

final https://www.mofga.org/status 200time 2217msstack cloudflare · WP Rocket 3.23.1.1

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
accelerometer=(), ambient-light-sensor=(), battery=(), camera=(), cross-origin-isolated=(), display-capture=(), document
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:_spf.mlsend.com include:_spf.google.com ip4:91.216.18.0/24 include:spf.constantcontact.com include:shops.shopify.com exists:%{i}._spf.mta.salesforce.com ~all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:rtt_admin@mofga.org
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
pearl.ns.cloudflare.com tadeo.ns.cloudflare.com

✓Registered with Network Solutions, LLC29.4 years old
mofga.org
✓Registration expiry2778 days
2034-04-16
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
pearl.ns.cloudflare.com tadeo.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
23.227.38.74 store.mofga.org +4	80443205220532082208320862087+5	0	Cloudflare~	—
172.66.175.142 mofga.org +3	80443205220532082208320862087+3	0	Cloudflare~	—
104.20.33.244 mofga.org +3	80443208220832086208720968080+2	0	Cloudflare~	—
149.210.171.6 pumphouse.mofga.org +1	21225380110443993995+2	48	direct	—
192.136.166.69 vpn.mofga.org +2	80443	0	direct	—
54.243.70.148 fairstore.mofga.org +1	none known	0	direct	—

Archived URLs

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

mofga.org security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames