Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 3 FIX

Security Headers

Action

2 of 10 headers properly configured

FIX

2 of 10 headers properly configured

HSTS header is missing

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options header is missing

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

X-Frame-Options has unexpected value

Got: SAMEORIGIN? Expected: DENY or SAMEORIGIN

Referrer-Policy header is missing

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Permissions-Policy header is missing

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Content-Security-Policy header is missing

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'

Cross-Origin-Opener-Policy is properly configured

Got: same-origin

Cross-Origin-Embedder-Policy is set

Got: require-corp

X-Powered-By header reveals technology stack

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Got: ASP.NET

Server header reveals version information

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

Got: Microsoft-IIS/10.0

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Learn more ▾

HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.

Source: RFC 6797 / OWASP

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'

Why this matters

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies or rewrite the page is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever.

Source: OWASP / MDN

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

Expected: DENY or SAMEORIGIN

Why this matters

An unrecognized X-Frame-Options value falls back to browser default behavior — clickjacking protection silently disabled.

Learn more ▾

X-Frame-Options accepts only DENY, SAMEORIGIN, or ALLOW-FROM (deprecated). Anything else (including typos like SAMEORIGN, or modern CSP-style frame-ancestors values shoved in by mistake) is ignored. The header LOOKS protective but isn't. Use `X-Frame-Options: DENY` plus `Content-Security-Policy: frame-ancestors 'none'` for defense in depth.

Source: MDN X-Frame-Options

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Why this matters

X-Powered-By: PHP/7.4.3 advertises your stack to attackers — disable it.

Learn more ▾

X-Powered-By and similar headers (X-AspNet-Version, X-Runtime) tell attackers which versions to target. Disable in your server/framework config: PHP `expose_php=Off`, ASP.NET `<httpRuntime enableVersionHeader="false">`, Express `app.disable('x-powered-by')`.

Source: OWASP

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

Content Security Policy

Action

No enforcing CSP policy found

FIX

No enforcing CSP policy found

No Content-Security-Policy header found

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'

Why this matters

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever. Start in Report-Only mode, fix violations, then graduate to enforcing.

Source: OWASP / MDN

Permissions-Policy

Action

No header set

FIX

No header set

No Permissions-Policy header

Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()

Subresource Integrity

Action

4 of 7 external resources have SRI

REVIEW

4 of 7 external resources have SRI

script from cdn.jsdelivr.net has SRI protection

External script from e.cdnpi.pe lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //e.cdnpi.pe/js/custom.8.7.min.js

External script from e.cdnpi.pe lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //e.cdnpi.pe/js/lord/icon.js

External link from fonts.googleapis.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://fonts.googleapis.com/css2?family=Poppins&display=swap

SRI Coverage 4 / 7 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	cdn.jsdelivr.net	✓ Protected
<script>	cdn.jsdelivr.net	✓ Protected
<script>	cdn.jsdelivr.net	✓ Protected
<script>	cdn.jsdelivr.net	✓ Protected
<script>	e.cdnpi.pe	✗ Missing
<script>	e.cdnpi.pe	✗ Missing
<link>	fonts.googleapis.com	✗ Missing

CORS Configuration

No CORS headers

REVIEW

No CORS headers

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

security.txt

Published with 0 contact(s)

REVIEW

security.txt

Expires: 2035-08-26T00:00:00.000Z

Encryption: https://builtwith.com/.well-known/publickey.txt

Transport Security

HTTP/3, HSTS, and TLS version analysis

REVIEW

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

Missing Strict-Transport-Security header

HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.

A+

TLS & Certificates

TLS 1.2, 7 checks passed

PASS

TLS 1.2, 7 checks passed

TLS 1.2 is used

Got: TLS 1.2

TLS 1.3 is not negotiated

TLS 1.3 offers improved performance and security. Consider enabling it.

Got: TLS 1.2

Strong cipher suite is used

Got: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

HTTP/2 is not negotiated

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

Got: http/1.1

Certificate is valid (expires in 53 days)

Got: 2026-06-15T17:18:19Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: builtwith.com, builtwith.ie

Certificate is issued by a trusted CA

Got: CN=R12,O=Let's Encrypt,C=US

TLS 1.3 offers improved performance and security. Consider enabling it.

Why this matters

TLS 1.3 not in use — connection falls back to 1.2 and pays the extra round-trip.

Learn more ▾

Most clients prefer TLS 1.3 if both sides support it. If your server has TLS 1.3 enabled but it's not being negotiated, check for a downgrade-attack mitigation issue or a misconfigured cipher list. nginx ≥ 1.13.0 and OpenSSL ≥ 1.1.1 support TLS 1.3.

Source: RFC 8446 / Mozilla SSL Config

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.2

Cipher Suite

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=builtwith.comIssuer CN=R12,O=Let's Encrypt,C=USValid 2026-03-17T17:18:20Z → 2026-06-15T17:18:19ZExpires in 53 days SANs builtwith.com, builtwith.ieSignature SHA256-RSASerial 6eaa0f4110b12a67e85ba33e8a92ad9f3a4

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 324 days Signature SHA256-RSASerial c212324b70a9b49171dc40f7e285263c

Cookie Security

1 cookies analyzed, 2 checks passed

PASS

1 cookies analyzed, 2 checks passed

Cookie 'ASP.NET_SessionId' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'ASP.NET_SessionId' has the HttpOnly flag

Cookie 'ASP.NET_SessionId' has SameSite=Lax

1 cookies analyzed 1 critical

Name	Secure	HttpOnly	SameSite	Size	Issues
ASP.NET_SessionId	✗	✓	Lax	41 B	1

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

security.txt is present — good practice

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✗ Exposed	Security Policy	Info

Email Security

DMARC: quarantine

PASS

DMARC: quarantine

DMARC policy is quarantine — good protection

DMARC

Policy quarantine — good protection Record v=DMARC1; p=quarantine; pct=100; rua=mailto:re+gbiqj290uaa@dmarc.postmarkapp.com; sp=none; aspf=r;

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.