golfiv.fr security report

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

69risk

Elevated

Several issues worth triaging this week.

0Critical

1High

8Medium

5Low

2Info

Collected 13 hours ago3.6sfrom cache

Certificate Transparency9
DNS resolution9
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs6
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis16

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.

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.golfiv.fr TXT "v=DMARC1; p=none; rua=mailto:dmarc@golfiv.fr"`, review the reports, then move to p=quarantine and p=reject.
asset: golfiv.fr
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: 37.187.148.167: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://www.golfiv.fr/
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.golfiv.fr/
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://www.golfiv.fr/
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://www.golfiv.fr/
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://www.golfiv.fr/
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://www.golfiv.fr/
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: golfiv.fr
37.187.148.167 (golfiv.fr) reports openssh 8.4p1. 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: 37.187.148.167
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 37.187.148.167:25
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://www.golfiv.fr/
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://www.golfiv.fr/
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: golfiv.fr
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: golfiv.fr
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: golfiv.fr

final https://www.golfiv.fr/status 200time 2080msstack cloudflare

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

✗Cookie phpbb3_enor8_u
no Secure · HttpOnly · no SameSite
✗Cookie phpbb3_enor8_k
no Secure · HttpOnly · no SameSite
✗Cookie phpbb3_enor8_sid
no Secure · HttpOnly · no SameSite

✓Receives mail via 1 server
mail.golfiv.fr
!SPFends in ~all
v=spf1 ip4:37.187.148.167 ~all
✗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
dns15.ovh.net ns15.ovh.net

✓Registered with OVH19.9 years old
golfiv.fr
✓Registration expiry301 days
2027-07-05
✗Transfer lock
none
✓2 nameservers at registry
dns15.ovh.net ns15.ovh.net

Address	Ports	CVEs	Edge	Network
37.187.148.167 golfiv.fr +8	222580143443587	0	direct	—

Archived URLs

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

golfiv.fr security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames