Back to results

Digital exposure report

guardicore.com

High exposure. Significant weaknesses put the brand, customers and email at risk.

Scanned: 2026-11-21 09:50 UTC

Partial coverage: the score is based on 52% of applicable check weight. 8 unverified check(s) are excluded, not counted as failures.

D
69/100

What to do first

  1. 1.

    Tell receiving mail servers how to treat fake email from your domain

    Without this policy, inboxes have less guidance for spotting messages that impersonate you.

    Who can fix it: Your email provider, together with whoever manages your DNS

    How to verify after the fix

    dig +short TXT _dmarc.guardicore.com
  2. 2.

    Choose which companies may issue certificates for your domain

    This reduces the chance of a certificate being issued by a provider you did not choose.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short CAA guardicore.com

A starting point, not a security guarantee.

What this grade means

Tested hostname
guardicore.com
Website request
GET https://guardicore.com/
Scan time
2026-11-21 09:50:09 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • HTTPS available · Unverified
  • SSL/TLS certificate validity · Unverified
  • HSTS — enforce encryption in the browser · Unverified
  • CSP — protection from script injection · Unverified
  • Clickjacking protection · Unverified
  • X-Content-Type-Options · Unverified
  • Referrer-Policy · Unverified
  • Permissions-Policy · Unverified

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security19/30Spoofing email in the company's name is possible in some cases.
Encryption & certificate7/7Traffic to the site is encrypted and the certificate is valid.
Browser protections—Nothing in this category could be verified from public data.
DNS infrastructure10/15The domain's infrastructure works, but recommended hardening is missing.

Fix priorities

  1. 1.MediumDMARC — anti-spoofing policy · Hardening gap+19
  2. 2.LowCAA — who may issue certificates · Hardening gap+10

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • HTTPS available
  • SSL/TLS certificate validity
  • CSP — protection from script injection
  • HSTS — enforce encryption in the browser
  • Clickjacking protection
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 9/10

An authorized sender list is defined; mail from other servers is flagged as suspicious.

~all (softfail) — acceptable when combined with enforced DMARC. 5 of 10 DNS lookups.

Source data: DNS TXT guardicore.com
v=spf1 ip4:34.202.195.232 ip4:34.198.183.12 include:_spf.google.com include:aspmx.pardot.com include:_spf.salesforce.com include:_spf.atlassian.net include:amazonses.com ~all
$ dig +short TXT guardicore.com
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Needs attention · Severity: Medium · Hardening gap · 5/15

DMARC is in monitoring mode only — forged email still reaches recipients.

Policy p=none. p=none collects reports but does not protect.

Source data: DNS TXT _dmarc.guardicore.com
v=DMARC1; p=none; rua=mailto:dmarcalerts@guardicore.com; ruf=mailto:dmarcalerts@guardicore.com
$ dig +short TXT _dmarc.guardicore.com
Fix recommendation (effort: Medium)
  1. Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
  2. Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
  3. Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.guardicore.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@guardicore.com; fo=1"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.

Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.

DKIM public key found for selector: google, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.guardicore.com
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCVtGsmyNCX8WVc7txXfz+O7uvYl4RGNXzD…
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw1gU64wM331J2x42nJ5l0VWV9mz2yyXO…
s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8tvSmzHnj/KkHIVAuonmai05ZFiat3Js8GETY…
$ dig +short TXT google._domainkey.guardicore.com
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX guardicore.com
10 mx0a-00190b01.pphosted.com
20 mx0b-00190b01.pphosted.com
$ dig +short MX guardicore.com
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Unverified · Severity: OK · Not scored

HTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.

Requesting https://guardicore.com/ didn't complete (HTTP 521). Timeouts and transport errors may be transient; the check is excluded from the score.

Source data: HTTPS GET https://guardicore.com/
HTTP 521
$ curl -svI https://guardicore.com/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://www.guardicore.com

Source data: HTTP GET http://guardicore.com/ (redirects not followed)
HTTP 301
Location: https://www.guardicore.com
$ curl -sI http://guardicore.com/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Unverified · Severity: OK · Not scored

The certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.

No live TLS evidence was obtained. CT entries are shown as context only. Not scored.

Source data: Certificate Transparency logs (certspotter) for guardicore.com
No valid certificate found in CT logs
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect guardicore.com:443 -servername guardicore.com 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://guardicore.com/
No HTTPS response received
$ curl -sIL https://guardicore.com/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Passed · Severity: OK · 7/7

The domain's records are digitally signed and hard to forge.

An AD (Authenticated Data) flag was returned by a validating resolver.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = true
$ dig +dnssec guardicore.com | grep -E "flags:.* ad"
Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA guardicore.com
(no CAA records found)
$ dig +short CAA guardicore.com
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
guardicore.com.  CAA  0 issue "letsencrypt.org"
guardicore.com.  CAA  0 iodef "mailto:security@guardicore.com"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

3 NS servers.

Source data: DNS NS guardicore.com
ns-36-c.gandi.net
ns-232-b.gandi.net
ns-235-a.gandi.net
$ dig +short NS guardicore.com
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rules1 observed gaps
  • PCI DSS v4.05 unverified
  • NIS2 / vendor due diligence2 observed gaps · 3 unverified
  • SOC 2 / ISO 27001 baseline1 observed gaps · 6 unverified

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Aguardicore.com217.70.184.38
AAAAguardicore.com—
MXguardicore.com10 mx0a-00190b01.pphosted.com | 20 mx0b-00190b01.pphosted.com
NSguardicore.comns-36-c.gandi.net | ns-232-b.gandi.net | ns-235-a.gandi.net
TXTguardicore.comMS=ms12377110 | MS=ms65715838 | MS=ms80066537 | ZOOM_verify_m7YPbwJL18ZaJqURyayc8X | ca3-8c72f3a184974094b9f30a5961b2bb24 | dropbox-domain-verification=kkraq67za78q | miro-verification=66bbc641659960e91627c23d9baa37c4773af27c | google-site-verification=HE1r2Evbp-uhkrfbYH9NRcrdpIZ8CsBwEY89V55RCD4 | google-site-verification=kIdsFOhuOOMOxfiOWGRctB044a2I5OjHLuTMT_8V4R8 | pardot503441=9fddb911a99f13ffd31d6f8a2d636f3b5b7055addf83fd4d329b38c408e73a17 | atlassian-domain-verification=B1em/osrEOEoZE9T5rxuPfe66Uy4/fesB7oWAYJ3kl/iYkvfIszW6stn3aCdHcsc | v=spf1 ip4:34.202.195.232 ip4:34.198.183.12 include:_spf.google.com include:aspmx.pardot.com include:_spf.salesforce.com include:_spf.atlassian.net include:amazonses.com ~all
TXT_dmarc.guardicore.comv=DMARC1; p=none; rua=mailto:dmarcalerts@guardicore.com; ruf=mailto:dmarcalerts@guardicore.com
CAAguardicore.com—
DSguardicore.com30037 13 2 15163bfb878a4289cf9632769dc4d4eebe0ce2c793b5aa86ec9ff5928761574b
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain