Skip to content
https://www.anaconfort.ro

Security

· 33 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
75
GRADE
C
FIX
8
REVIEW
7
PASS
18
INFO
0
Checks
33
18 PASS 7 REVIEW 8 FIX
D
Security Headers
Action
3 of 10 headers properly configured
FIX
3 of 10 headers properly configured
Warning::
HSTS is enabled but 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: SAMEORIGIN
Warning::
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
Warning::
Permissions-Policy header is missing
Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
Expected: geolocation=(), camera=(), microphone=()
Critical::
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'
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Warning::
X-Powered-By header reveals technology stack
This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.
Got: Gomag
Info::
Server header is present without version info
Got: Caddy
Info::
Domain is not in the Chrome HSTS preload list (status: unknown)
Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).
Got: unknown

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

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

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

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin
Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp
Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

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

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

F
Content Security Policy
Action
No enforcing CSP policy found
FIX
No enforcing CSP policy found
Critical::
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

D
Cross-Origin Tab Safety
Action
7 of 12 new-tab link(s) missing rel=noopener
FIX
7 of 12 new-tab link(s) missing rel=noopener
Warning::
7 link(s) open in a new tab without rel=noopener
Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.
D
CSP Inline-Style Readiness
Action
177 inline style attribute(s) detected
FIX
177 inline style attribute(s) detected
Warning::
177 inline style attribute(s) detected
Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 177 inline style(s) is high. Affected element types include: body, div, img, i, h2. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.
F
Subresource Integrity Adoption
Action
0% SRI adoption (0/26 third-party resources)
FIX
0% SRI adoption (0/26 third-party resources)
Warning::
SRI adoption: 0/26 third-party resources protected (0%)
Of 26 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource. Missing SRI on (first 5 examples): - https://www.gstatic.com/firebasejs/8.10.0/firebase-messaging.js - https://analytics.tiktok.com/i18n/pixel/static/identify_2a73ddc0.js - https://www.gstatic.com/firebasejs/8.10.0/firebase-app.js - https://analytics.tiktok.com/i18n/pixel/static/main.MWRhY2RiNmFkMA.js - https://connect.facebook.net/signals/config/303927263363896?v=2.9.397&r=stable&domain=www.anaconfort.ro&hme=457e068698591ac437afb4b2e5fbe0266b08712615b8792436a91385ebda0da3&ex_m=115%2C227%2C166%2C26%2C80%2C81%2C158%2C76%2C75%2C11%2C176%2C100%2C20%2C150%2C138%2C45%2C83%2C88%2C146%2C171%2C178%2C31%2C17%2C30%2C18%2C32%2C33%2C34%2C36%2C54%2C159%2C85%2C123%2C22%2C24%2C50%2C46%2C48%2C47%2C93%2C102%2C106%2C121%2C157%2C160%2C52%2C122%2C28%2C25%2C130%2C77%2C42%2C162%2C161%2C163%2C154%2C152%2C29%2C41%2C65%2C120%2C173%2C78%2C21%2C125%2C91%2C74%2C23%2C95%2C96%2C127%2C94%2C148%2C147%2C151%2C107%2C172%2C175%2C40%2C55%2C124%2C53%2C8%2C4%2C5%2C7%2C6%2C3%2C101%2C112%2C180%2C179%2C194%2C241%2C82%2C255%2C254%2C253%2C14%2C27%2C39%2C61%2C114%2C67%2C10%2C71%2C108%2C109%2C110%2C116%2C141%2C37%2C35%2C143%2C144%2C145%2C140%2C139%2C167%2C84%2C170%2C168%2C169%2C56%2C66%2C134%2C19%2C174%2C51%2C305%2C306%2C307%2C304%2C320%2C344%2C234%2C223%2C68%2C224%2C222%2C347%2C338%2C58%2C235%2C118%2C142%2C90%2C132%2C60%2C131%2C137%2C136%2C64%2C72%2C70%2C164%2C86%2C87%2C126%2C43%2C38%2C59%2C62%2C111%2C177%2C1%2C135%2C16%2C133%2C12%2C2%2C63%2C103%2C15%2C73%2C69%2C129%2C99%2C98%2C182%2C183%2C104%2C105%2C9%2C113%2C181%2C57%2C155%2C97%2C89%2C79%2C128%2C117%2C49%2C156%2C0%2C92%2C149%2C153%2C165%2C44%2C119%2C13%2C184%2C251%2C249%2C244%2C246%2C247%2C248%2C245%2C233%2C250%2C252%2C243%2C258%2C201%2C202%2C334%2C337%2C336%2C333%2C335%2C257%2C215%2C209%2C213%2C214%2C212%2C207%2C200%2C196%2C199%2C260%2C373%2C286%2C290%2C293%2C294%2C295%2C291%2C296%2C289%2C284%2C298%2C299%2C288%2C297%2C301%2C292%2C287%2C300%2C302%2C285%2C226%2C283%2C218%2C210%2C211%2C237%2C208%2C206%2C232%2C363%2C259%2C228%2C197%2C198%2C195%2C193%2C204%2C205%2C203%2C308%2C365%2C328%2C329%2C331%2C330%2C327%2C326%2C216%2C262%2C269%2C270%2C271%2C263%2C265%2C268%2C266%2C267%2C264%2C261%2C281%2C275%2C278%2C274%2C282%2C279%2C273%2C277%2C280%2C276%2C272%2C322%2C341 Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.
Got: 0% (0/26)
F
Subresource Integrity
Action
0 of 26 external resources have SRI
FIX
0 of 26 external resources have SRI
Warning::
External script from www.gstatic.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.gstatic.com/firebasejs/8.10.0/firebase-messaging.js
Warning::
External script from analytics.tiktok.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://analytics.tiktok.com/i18n/pixel/static/identify_2a73ddc0.js
Warning::
External script from www.gstatic.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.gstatic.com/firebasejs/8.10.0/firebase-app.js
Warning::
External script from analytics.tiktok.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://analytics.tiktok.com/i18n/pixel/static/main.MWRhY2RiNmFkMA.js
Warning::
External script from connect.facebook.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://connect.facebook.net/signals/config/303927263363896?v=2.9.397&r=stable&domain=www.anaconfort.ro&hme=457e068698591ac437afb4b2e5fbe0266b08712615b8792436a91385ebda0da3&ex_m=115%2C227%2C166%2C26%2C80%2C81%2C158%2C76%2C75%2C11%2C176%2C100%2C20%2C150%2C138%2C45%2C83%2C88%2C146%2C171%2C178%2C31%2C17%2C30%2C18%2C32%2C33%2C34%2C36%2C54%2C159%2C85%2C123%2C22%2C24%2C50%2C46%2C48%2C47%2C93%2C102%2C106%2C121%2C157%2C160%2C52%2C122%2C28%2C25%2C130%2C77%2C42%2C162%2C161%2C163%2C154%2C152%2C29%2C41%2C65%2C120%2C173%2C78%2C21%2C125%2C91%2C74%2C23%2C95%2C96%2C127%2C94%2C148%2C147%2C151%2C107%2C172%2C175%2C40%2C55%2C124%2C53%2C8%2C4%2C5%2C7%2C6%2C3%2C101%2C112%2C180%2C179%2C194%2C241%2C82%2C255%2C254%2C253%2C14%2C27%2C39%2C61%2C114%2C67%2C10%2C71%2C108%2C109%2C110%2C116%2C141%2C37%2C35%2C143%2C144%2C145%2C140%2C139%2C167%2C84%2C170%2C168%2C169%2C56%2C66%2C134%2C19%2C174%2C51%2C305%2C306%2C307%2C304%2C320%2C344%2C234%2C223%2C68%2C224%2C222%2C347%2C338%2C58%2C235%2C118%2C142%2C90%2C132%2C60%2C131%2C137%2C136%2C64%2C72%2C70%2C164%2C86%2C87%2C126%2C43%2C38%2C59%2C62%2C111%2C177%2C1%2C135%2C16%2C133%2C12%2C2%2C63%2C103%2C15%2C73%2C69%2C129%2C99%2C98%2C182%2C183%2C104%2C105%2C9%2C113%2C181%2C57%2C155%2C97%2C89%2C79%2C128%2C117%2C49%2C156%2C0%2C92%2C149%2C153%2C165%2C44%2C119%2C13%2C184%2C251%2C249%2C244%2C246%2C247%2C248%2C245%2C233%2C250%2C252%2C243%2C258%2C201%2C202%2C334%2C337%2C336%2C333%2C335%2C257%2C215%2C209%2C213%2C214%2C212%2C207%2C200%2C196%2C199%2C260%2C373%2C286%2C290%2C293%2C294%2C295%2C291%2C296%2C289%2C284%2C298%2C299%2C288%2C297%2C301%2C292%2C287%2C300%2C302%2C285%2C226%2C283%2C218%2C210%2C211%2C237%2C208%2C206%2C232%2C363%2C259%2C228%2C197%2C198%2C195%2C193%2C204%2C205%2C203%2C308%2C365%2C328%2C329%2C331%2C330%2C327%2C326%2C216%2C262%2C269%2C270%2C271%2C263%2C265%2C268%2C266%2C267%2C264%2C261%2C281%2C275%2C278%2C274%2C282%2C279%2C273%2C277%2C280%2C276%2C272%2C322%2C341
Warning::
External script from connect.facebook.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://connect.facebook.net/signals/config/1488772372571257?v=2.9.397&r=stable&domain=www.anaconfort.ro&hme=457e068698591ac437afb4b2e5fbe0266b08712615b8792436a91385ebda0da3&ex_m=115%2C227%2C166%2C26%2C80%2C81%2C158%2C76%2C75%2C11%2C176%2C100%2C20%2C150%2C138%2C45%2C83%2C88%2C146%2C171%2C178%2C31%2C17%2C30%2C18%2C32%2C33%2C34%2C36%2C54%2C159%2C85%2C123%2C22%2C24%2C50%2C46%2C48%2C47%2C93%2C102%2C106%2C121%2C157%2C160%2C52%2C122%2C28%2C25%2C130%2C77%2C42%2C162%2C161%2C163%2C154%2C152%2C29%2C41%2C65%2C120%2C173%2C78%2C21%2C125%2C91%2C74%2C23%2C95%2C96%2C127%2C94%2C148%2C147%2C151%2C107%2C172%2C175%2C40%2C55%2C124%2C53%2C8%2C4%2C5%2C7%2C6%2C3%2C101%2C112%2C180%2C179%2C194%2C241%2C82%2C255%2C254%2C253%2C14%2C27%2C39%2C61%2C114%2C67%2C10%2C71%2C108%2C109%2C110%2C116%2C141%2C37%2C35%2C143%2C144%2C145%2C140%2C139%2C167%2C84%2C170%2C168%2C169%2C56%2C66%2C134%2C19%2C174%2C51%2C305%2C306%2C307%2C304%2C320%2C344%2C234%2C223%2C68%2C224%2C222%2C347%2C338%2C58%2C235%2C118%2C142%2C90%2C132%2C60%2C131%2C137%2C136%2C64%2C72%2C70%2C164%2C86%2C87%2C126%2C43%2C38%2C59%2C62%2C111%2C177%2C1%2C135%2C16%2C133%2C12%2C2%2C63%2C103%2C15%2C73%2C69%2C129%2C99%2C98%2C182%2C183%2C104%2C105%2C9%2C113%2C181%2C57%2C155%2C97%2C89%2C79%2C128%2C117%2C49%2C156%2C0%2C92%2C149%2C153%2C165%2C44%2C119%2C13%2C184
Warning::
External script from connect.facebook.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //connect.facebook.net/en_US/fbevents.js
Warning::
External script from t.themarketer.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://t.themarketer.com/t/j/ZOSGNZZZ
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtm.js?id=GTM-P25SB49X
Warning::
External script from analytics.tiktok.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://analytics.tiktok.com/i18n/pixel/events.js?sdkid=D3SCKO3C77U816ES5P30&lib=ttq
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/lazysizes.min.js?v=102511508-4.311
Warning::
External link from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/_fonts/Open-Sans.css
Warning::
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:wght@200;300;400;500;600;700&display=swap
Warning::
External link from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/css/main-min-v2.css?v=102511508-4.311-1
Warning::
External link from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/css/dev-style.css?v=102511508-4.311-1
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-GJRSNV4Y8H
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/jquery-2.1.4.min.js
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/jquery.autocomplete.js?v=20181023
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/gomag.config.js?v=102511508-4.311
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/gomag.js?v=102511508-4.311
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-GJRSNV4Y8H
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/plugins.js?v=102511508-4.311
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/plugins-async.js?v=102511508-4.311
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/menu-mobile.js?v=102511508-4.311
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/dev.js?v=102511508-4.311
Warning::
External script from gomagcdn.ro lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://gomagcdn.ro/themes/fashion/js/library.js?v=102511508-4.311
SRI Coverage 0 / 26 of external resources have integrity hashes
TagDomainIntegrity
<script>www.gstatic.com Missing
<script>analytics.tiktok.com Missing
<script>www.gstatic.com Missing
<script>analytics.tiktok.com Missing
<script>connect.facebook.net Missing
<script>connect.facebook.net Missing
<script>connect.facebook.net Missing
<script>t.themarketer.com Missing
<script>www.googletagmanager.com Missing
<script>analytics.tiktok.com Missing
<script>gomagcdn.ro Missing
<link>gomagcdn.ro Missing
<link>fonts.googleapis.com Missing
<link>gomagcdn.ro Missing
<link>gomagcdn.ro Missing
<script>www.googletagmanager.com Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>www.googletagmanager.com Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
<script>gomagcdn.ro Missing
F
Email Security
Action
no DMARC, no SPF
FIX
no DMARC, no SPF
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
Warning::
No SPF record found
Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
Info::
No DKIM detected via common selectors
DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
Info::
MTA-STS not configured
MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
Info::
TLS-RPT not configured
TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
Info::
BIMI not configured
BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.
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. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

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

Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

Why this matters

No DKIM signature on outbound mail — receivers can't cryptographically prove the message came from your domain.

Learn more

DKIM signs outbound mail with a private key whose public half lives in DNS at <selector>._domainkey.<domain>. Without DKIM, DMARC alone can't tell legitimate mail from spoofs, and large mailbox providers (Gmail, Yahoo) increasingly require DKIM for inbox placement. Note: this check probes a curated list of common selectors; non-standard selectors produce a false negative.

Source: RFC 6376 / Google + Yahoo 2024 sender requirements

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

D
Permissions-Policy
Action
No header set
FIX
No header set
Warning::
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=()
B
Cookie Security
1 cookies analyzed, 0 checks passed
REVIEW
1 cookies analyzed, 0 checks passed
Critical::
Cookie '6b7d13e357893cc7e146f269beb6d0bd' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie '6b7d13e357893cc7e146f269beb6d0bd' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie '6b7d13e357893cc7e146f269beb6d0bd' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
1 cookies analyzed 1 critical 2 warnings
NameSecureHttpOnlySameSiteSizeIssues
6b7d13e357893cc7e146f269beb6d0bd58 B3
B
WAF / Bot Protection
No WAF detected via response headers
REVIEW
No WAF detected via response headers
Info::
No WAF detected
Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.
B
security.txt
Vulnerability disclosure policy
REVIEW
Vulnerability disclosure policy
Info::
security.txt found
Got: https://www.anaconfort.ro/security.txt
Warning::
security.txt: Missing required 'Contact' field
Warning::
security.txt: Missing required 'Expires' field (RFC 9116)

security.txt

C
Permissions-Policy Granularity
Action
No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin
REVIEW
No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin
Warning::
Permissions-Policy header not set -- features default to allow-on-same-origin
Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need: ``` Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=() ``` Features the page legitimately uses can stay enabled with `feature=(self)`.
Got: header absent
B
Referrer-Policy Strictness
Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)
REVIEW
Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)
Info::
Referrer-Policy header not set -- browser default applies
Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior: ``` Referrer-Policy: strict-origin-when-cross-origin ``` This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.
Got: header absent
C
CORS Configuration
Action
Origin: *
REVIEW
Origin: *
Info::
Access-Control-Allow-Origin: * — unrestricted
Any website can read this resource's response. Appropriate for public APIs but not for user-specific content.
Info::
Origin reflection not testable with a single request
Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header.
CORS Configuration Permissive
Allow-Origin *Allow-Methods GET

Any website can read responses from this resource.

HeaderValueStatus
Access-Control-Allow-Origin*
Access-Control-Allow-MethodsGET

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
C
Known vulnerability matches
Action
6 known vulnerability match(es) against detected tech
REVIEW

Known Vulnerabilities

LibraryVersionSeveritySummaryFixed In
jQuery2.1.4mediumparseHTML() executes scripts in event handlers2.2.0
jQuery2.1.4medium3rd party CORS request may execute3.0.0-beta1
jQuery2.1.4mediumjQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution3.4.0
jQuery2.1.4mediumRegex in its jQuery.htmlPrefilter sometimes may introduce XSS3.5.0
jQuery2.1.4mediumpassing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.3.5.0
jQuery2.1.4lowjQuery 1.x and 2.x are End-of-Life and no longer receiving security updates2.999.999
A+
TLS & Certificates
TLS 1.3, 9 checks passed
PASS
TLS 1.3, 9 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_CHACHA20_POLY1305_SHA256
Info::
HTTP/2 is negotiated
Got: h2
Info::
OCSP stapling enabled
Info::
Certificate is valid (expires in 69 days)
Got: 2026-11-18T23:59:59Z
Info::
Certificate chain has 3 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA256
Info::
Certificate covers 1 domain(s)
Got: www.anaconfort.ro
Info::
Certificate is issued by a trusted CA
Got: CN=ZeroSSL ECC DV SSL CA 2,O=ZeroSSL GmbH,C=AT
Connection
Protocol
TLS 1.3
Cipher Suite
TLS_CHACHA20_POLY1305_SHA256
HTTP Version
h2 (HTTP/2)

Certificate Chain

Leaf Certificate
Subject CN=www.anaconfort.roIssuer CN=ZeroSSL ECC DV SSL CA 2,O=ZeroSSL GmbH,C=ATValid 2026-08-20T00:00:00Z → 2026-11-18T23:59:59ZExpires in 69 days SANs www.anaconfort.roSignature ECDSA-SHA256Serial bcb86058b4583540105767348060d391
Intermediate (CA Certificate)
Subject CN=ZeroSSL ECC DV SSL CA 2,O=ZeroSSL GmbH,C=ATIssuer CN=Sectigo Public Server Authentication Root E46,O=Sectigo Limited,C=GBValid 2025-09-24T00:00:00Z → 2035-09-23T23:59:59ZExpires in 3300 days Signature ECDSA-SHA384Serial c4e1c5bb00f0278f347be4f85d63fcca
Intermediate (CA Certificate)
Subject CN=Sectigo Public Server Authentication Root E46,O=Sectigo Limited,C=GBIssuer CN=USERTrust ECC Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=USValid 2021-03-22T00:00:00Z → 2038-01-18T23:59:59ZExpires in 4148 days Signature ECDSA-SHA384Serial 1a9eafec6de8e19b5c193141b68d90dd
A+
Trusted Types (XSS Sink Hardening)
No CSP header -- Trusted Types check is N/A
PASS
No CSP header -- Trusted Types check is N/A
Info::
No CSP header found -- Trusted Types check is N/A
A+
Bot Challenge Detection
Scan reached real page content (no bot-protection interstitial)
PASS
Scan reached real page content (no bot-protection interstitial)
Info::
No bot-protection interstitial detected -- the rest of the report reflects the real page
A+
Soft-404 Detection
No soft-404 patterns detected in page title or headings
PASS
No soft-404 patterns detected in page title or headings
Info::
No soft-404 patterns detected in page title or headings
A+
Empty Page Detection
Page has substantive body text and no placeholder / template-leak signals
PASS
Page has substantive body text and no placeholder / template-leak signals
Info::
Page has substantive body text and no placeholder / template-leak signals
A+
Geo-Restriction Detection
No geo-restriction signals detected -- scan reached the page from an allowed region
PASS
No geo-restriction signals detected -- scan reached the page from an allowed region
Info::
No geo-restriction detected
A+
Maintenance Mode Detection
No maintenance-mode signals detected -- scan reached a normal page
PASS
No maintenance-mode signals detected -- scan reached a normal page
Info::
No maintenance-mode signals detected
A
CORS Depth
1 CORS depth signal(s) detected
PASS
1 CORS depth signal(s) detected
Info::
CORS allows any origin (`Access-Control-Allow-Origin: *`)
Any website can fetch this URL via JavaScript and read the response body. Acceptable for genuinely public APIs (e.g. CDN-served static assets). Risky if the URL returns user-specific or session-derived data, since other origins can scrape it via the user's browser without needing credentials. Narrow Allow-Origin to a specific origin allow-list when the response is sensitive.
Got: Allow-Origin: *
A+
Source Map Exposure
No source maps accessible (probed 1 candidate URL(s))
PASS
No source maps accessible (probed 1 candidate URL(s))
Info::
No source maps accessible across 1 probed candidate(s)
A+
HTML Version Disclosure
No software-version disclosures in HTML
PASS
No software-version disclosures in HTML
Info::
No software-version disclosures in HTML
A+
Open Redirect Surface
No redirect-shaped query parameters in DOM links
PASS
No redirect-shaped query parameters in DOM links
Info::
No redirect-shaped query parameters in DOM links
A+
Auth Security
Page is not a login form -- auth-security checks are N/A
PASS
Page is not a login form -- auth-security checks are N/A
Info::
Page does not appear to be a login form
A+
Subdomain Inventory Exposure
No risky subdomain names in certificate SANs
PASS
No risky subdomain names in certificate SANs
Info::
No risky subdomain names in certificate SANs
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::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
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 Not foundSecurity Policy
/package.json Not founddependency-manifest
/composer.json Not founddependency-manifest
/Gemfile Not founddependency-manifest
/Gemfile.lock Not founddependency-manifest
/requirements.txt Not founddependency-manifest
/pom.xml Not founddependency-manifest
/.gitlab-ci.yml Not foundci-config
/.travis.yml Not foundci-config
A+
API Surface
No API specs or GraphQL introspection found (probed 11 candidate path(s))
PASS
No API specs or GraphQL introspection found (probed 11 candidate path(s))
Info::
No API specs or GraphQL introspection found (probed 11 path(s))
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