Skip to content
https://curl.se

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
9
INFO
0
Checks
12
9 PASS 2 REVIEW 1 FIX
F
Email Security
Action
No DMARC
FIX
No DMARC
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures.
DMARC

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
B
security.txt
Published with 1 contact(s)
REVIEW

security.txt

Contact: https://hackerone.com/curl
Expires: 2027-01-21T00:00:00Z
Policy: https://curl.se/.well-known/security.txt
A
Security Headers
8 of 10 headers properly configured
PASS
8 of 10 headers properly configured
Warning::
HSTS is missing includeSubDomains
Without includeSubDomains, subdomains can still be accessed over HTTP.
Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Info::
X-Frame-Options is properly configured
Got: deny
Info::
Referrer-Policy is properly configured
Got: strict-origin
Info::
Permissions-Policy is set
Got: accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), bluetooth=(), browsing-topics=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), execution-while-not-rendered=(), execution-while-out-of-viewport=(), fullscreen=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), idle-detection=(), local-fonts=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), speaker-selection=(), usb=(), web-share=(), xr-spatial-tracking=()
Info::
Content-Security-Policy is present
Got: upgrade-insecure-requests; block-all-mixed-content; default-src 'none'; img-src …
Info::
Cross-Origin-Opener-Policy is properly configured
Got: same-origin
Info::
Cross-Origin-Embedder-Policy is set
Got: require-corp
Info::
X-Powered-By header is not present
Warning::
Server header reveals version information
The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.
Got: nginx/1.27.5

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains
Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.

Why this matters

Server: nginx/1.18.0 tells attackers exactly which CVEs to test — strip the version string.

Learn more

Server version disclosure helps attackers select exploits matching your stack. Configure your server to omit the version (nginx: `server_tokens off;`, Apache: `ServerTokens Prod`). Doesn't fix vulnerabilities but removes the easy reconnaissance step.

Source: OWASP

A+
Content Security Policy
8 of 10 CSP checks passed
PASS
8 of 10 CSP checks passed
Info::
Raw CSP policy
Got: upgrade-insecure-requests; block-all-mixed-content; default-src 'none'; img-src 'self'; style-src 'unsafe-inline' 'self'; form-action 'self'; frame-ancestors 'none'; require-trusted-types-for 'script';
Info::
default-src directive is set
Got: default-src 'none'
Info::
No 'unsafe-inline' in script source
Info::
No 'unsafe-eval' in script source
Info::
No wildcard in script source
Info::
object-src falls back to default-src
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors 'none'
Info::
form-action directive is set
Got: form-action 'self'
Info::
upgrade-insecure-requests is enabled

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

Parsed Policy

upgrade-insecure-requests
block-all-mixed-content
default-src 'none'
img-src 'self'
style-src 'unsafe-inline''self'
form-action 'self'
frame-ancestors 'none'
require-trusted-types-for 'script'
A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 74 days)
Got: 2026-07-05T16:32:54Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 1 domain(s)
Got: curl.se
Info::
Certificate is issued by a trusted CA
Got: CN=R12,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection
Protocol
TLS 1.3
Cipher Suite
TLS_AES_128_GCM_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=curl.seIssuer CN=R12,O=Let's Encrypt,C=USValid 2026-04-06T16:32:55Z → 2026-07-05T16:32:54ZExpires in 74 days SANs curl.seSignature SHA256-RSASerial 54163dccaf342a6d1c632da387cd85340f2
Intermediate (CA Certificate)
Subject CN=R12,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 325 days Signature SHA256-RSASerial c212324b70a9b49171dc40f7e285263c
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
Subresource Integrity
No external resources
PASS
No external resources
Info::
No external resources to protect
SRI Coverage No external resources — SRI not applicable
A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
security.txt is present — good practice
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD Not foundVersion Control
/.git/config Not foundVersion Control
/.svn/entries Not foundVersion Control
/.env Not foundConfiguration
/.env.local Not foundConfiguration
/.env.production Not foundConfiguration
/wp-config.php Not foundConfiguration
/.htaccess Not foundConfiguration
/phpinfo.php Not foundDebug
/server-status Not foundDebug
/server-info Not foundDebug
/.well-known/security.txt ExposedSecurity PolicyInfo
A+
Permissions-Policy
31 directives, 0 missing
PASS
31 directives, 0 missing
Info::
accelerometer=() — blocked for all origins
Info::
ambient-light-sensor=() — blocked for all origins
Info::
autoplay=() — blocked for all origins
Info::
battery=() — blocked for all origins
Info::
bluetooth=() — blocked for all origins
Info::
browsing-topics=() — blocked for all origins
Info::
camera=() — blocked for all origins
Info::
display-capture=() — blocked for all origins
Info::
document-domain=() — blocked for all origins
Info::
encrypted-media=() — blocked for all origins
Info::
execution-while-not-rendered=() — blocked for all origins
Info::
execution-while-out-of-viewport=() — blocked for all origins
Info::
fullscreen=() — blocked for all origins
Info::
gamepad=() — blocked for all origins
Info::
geolocation=() — blocked for all origins
Info::
gyroscope=() — blocked for all origins
Info::
hid=() — blocked for all origins
Info::
idle-detection=() — blocked for all origins
Info::
local-fonts=() — blocked for all origins
Info::
magnetometer=() — blocked for all origins
Info::
microphone=() — blocked for all origins
Info::
midi=() — blocked for all origins
Info::
payment=() — blocked for all origins
Info::
picture-in-picture=() — blocked for all origins
Info::
publickey-credentials-get=() — blocked for all origins
Info::
screen-wake-lock=() — blocked for all origins
Info::
serial=() — blocked for all origins
Info::
speaker-selection=() — blocked for all origins
Info::
usb=() — blocked for all origins
Info::
web-share=() — blocked for all origins
Info::
xr-spatial-tracking=() — blocked for all origins

Raw Header

accelerometer=() ambient-light-sensor=() autoplay=() battery=() bluetooth=() browsing-topics=() camera=() display-capture=() document-domain=() encrypted-media=() execution-while-not-rendered=() execution-while-out-of-viewport=() fullscreen=() gamepad=() geolocation=() gyroscope=() hid=() idle-detection=() local-fonts=() magnetometer=() microphone=() midi=() payment=() picture-in-picture=() publickey-credentials-get=() screen-wake-lock=() serial=() speaker-selection=() usb=() web-share=() xr-spatial-tracking=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
accelerometer Blocked
ambient-light-sensor Blocked
autoplay Blocked
battery Blocked
bluetooth Blocked
browsing-topics Blocked
camera Blocked
display-capture Blocked
document-domain Blocked
encrypted-media Blocked
execution-while-not-rendered Blocked
execution-while-out-of-viewport Blocked
fullscreen Blocked
gamepad Blocked
geolocation Blocked
gyroscope Blocked
hid Blocked
idle-detection Blocked
local-fonts Blocked
magnetometer Blocked
microphone Blocked
midi Blocked
payment Blocked
picture-in-picture Blocked
publickey-credentials-get Blocked
screen-wake-lock Blocked
serial Blocked
speaker-selection Blocked
usb Blocked
web-share Blocked
xr-spatial-tracking Blocked
A+
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) supported
The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.
Info::
HSTS enabled (base policy)
Info::
HSTS missing includeSubDomains
Without includeSubDomains, HSTS only protects the exact domain.
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback