Back to results

Digital exposure report

box.com

Good shape, with a few gaps worth closing this quarter.

Scanned: 2026-11-15 19:22 UTC

Full coverage: every applicable check was assessed.

B
87/100

What to do first

  1. 1.

    Tell browsers to always use the secure version

    Helps browsers use HTTPS on future visits after they have received the policy.

    Who can fix it: Your web host

    How to verify after the fix

    curl -sIL https://box.com/ | grep -i "Strict-Transport-Security"
  2. 2.

    Limit what your site shares when visitors click links

    This reduces how much page address detail is passed to other websites.

    Who can fix it: Your website developer or web host

    How to verify after the fix

    curl -sIL https://box.com/ | grep -i "Referrer-Policy"

A starting point, not a security guarantee.

What this grade means

Tested hostname
box.com
Website request
GET https://box.com/ → https://www.box.com/
Scan time
2026-11-15 19:22:33 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
None. Every applicable check was assessed.

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 security29/30Spoofing email from this domain is hard.
Encryption & certificate25/25Traffic to the site is encrypted and the certificate is valid.
Browser protections18/30Some browser protections are missing.
DNS infrastructure15/15The domain's infrastructure is well hardened.

Fix priorities

  1. 1.MediumHSTS — enforce encryption in the browser · Hardening gap+4
  2. 2.LowReferrer-Policy · Hardening gap+3
  3. 3.LowPermissions-Policy · Hardening gap+2
  4. 4.LowCSP — protection from script injection · Hardening gap+3

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. 6 of 10 DNS lookups.

Source data: DNS TXT box.com
v=spf1 ip4:74.112.184.0/22 ip4:107.152.16.0/20 ip4:204.14.232.0/22 ip4:202.129.242.0/25 ip4:34.211.27.153 ip4:54.70.65.68  include:_spf.google.com include:sendgrid.net include:_spf.mxhero.com include:_spf.q4press.com include:stspg-customer.com include:5608010.spf08.hubspotemail.net ~all
$ dig +short TXT box.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

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.box.com
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:reports@dmarc.cyber.dhs.gov; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
$ dig +short TXT _dmarc.box.com
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, default, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.box.com
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCCjyrgz6Jn4cHBaRQzE/vFzh4ZxKQON/lA…
default._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzvfsB8l67iQSWK0Cr6Ej9WugUui8JMI0O…
k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLgkJPxctkdmPG2CNMLWuakvn303HixFv+rkJywyYp5…
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7mzRZHKPrWNGs/hCbw918LVmvmaSOH8k…
s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDOtVDKVkYZ44eWxiRm//i/H9ox0CwbXbJiZtdU…
$ dig +short TXT google._domainkey.box.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 box.com
10 mxa-00172704.gslb.pphosted.com
10 mxb-00172704.gslb.pphosted.com
$ dig +short MX box.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

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://box.com/ returned HTTP 200 (final URL: https://www.box.com/). Client-side certificate validation passed.

Source data: HTTPS GET https://box.com/
HTTP 200
Final URL: https://www.box.com/
$ curl -sIL https://box.com/
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://box.com:443/

Source data: HTTP GET http://box.com/ (redirects not followed)
HTTP 301
Location: https://box.com:443/
$ curl -sI http://box.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

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-05-28 (194 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.

Source data: Certificate Transparency logs (certspotter) for box.com
Live TLS handshake: certificate accepted
CT logs (context only, not scored):
Issuer: DigiCert
Valid from: 2026-11-11
Valid until: 2027-05-28
Names: *.blog.box.com, *.box.com, box.com
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect box.com:443 -servername box.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

Needs attention · Severity: Medium · Hardening gap · 4/8

Encryption enforcement is set for too short a time.

max-age=2592000 (30 days), includeSubDomains, preload. ≥ 180 days recommended.

Source data: Response headers from https://www.box.com/
Strict-Transport-Security: max-age=2592000; includeSubDomains; preload
$ curl -sIL https://box.com/ | grep -i "Strict-Transport-Security"
Fix recommendation (effort: Easy)
  1. Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
  2. Gradually raise it to 31536000 (one year) and add includeSubDomains.
  3. Consider preload only once the policy is stable — removal from the preload list is slow.
/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains

Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.

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

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

A script policy exists, but it's permissive and offers only partial protection.

script-src includes: 'unsafe-inline', a broad source (* / https: / data:) — weakens XSS protection.

Source data: Response headers from https://www.box.com/
Content-Security-Policy: default-src * 'self' blob: data: 'unsafe-inline'; font-src 'self' data: fonts.googleapis.com fonts.gstatic.com
$ curl -sIL https://box.com/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/*
  Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'

Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.

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

Passed · Severity: OK · 5/5

The site can't be embedded by foreign sites.

X-Frame-Options: SAMEORIGIN

Source data: Response headers from https://www.box.com/
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://box.com/ | grep -i "X-Frame-Options"
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

Passed · Severity: OK · 4/4

The browser won't guess file types in a way that could execute code.

nosniff is set.

Source data: Response headers from https://www.box.com/
X-Content-Type-Options: nosniff
$ curl -sIL https://box.com/ | grep -i "X-Content-Type-Options"
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

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://www.box.com/
Referrer-Policy: (missing)
$ curl -sIL https://box.com/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. Set Referrer-Policy: strict-origin-when-cross-origin.
/*
  Referrer-Policy: strict-origin-when-cross-origin

Safety: This change is made in your server/CDN settings. Test on staging before production.

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

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

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Source data: Response headers from https://www.box.com/
Permissions-Policy: (missing)
$ curl -sIL https://box.com/ | grep -i "Permissions-Policy"
Fix recommendation (effort: Easy)
  1. Disable browser features the site doesn't need (camera, microphone, geolocation).
/*
  Permissions-Policy: camera=(), microphone=(), geolocation=()

Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.

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)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://www.box.com/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://box.com/ | grep -iE "^(server|x-powered-by)"
Documentation: 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 box.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

Passed · Severity: OK · 5/5

Only authorized certificate authorities can issue certificates for the domain.

CAA records: 0 issue "digicert.com" | 0 issue "www.digicert.com"

Source data: DNS CAA box.com
0 issue "digicert.com"
0 issue "www.digicert.com"
$ dig +short CAA box.com
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.

8 NS servers.

Source data: DNS NS box.com
dns1.p09.nsone.net
dns2.p09.nsone.net
dns3.p09.nsone.net
dns4.p09.nsone.net
ns01.box-ns.com
ns02.box-ns.com
ns03.box-ns.com
ns04.box-ns.com
$ dig +short NS box.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 rulesNo gaps observed
  • PCI DSS v4.02 observed gaps
  • NIS2 / vendor due diligence1 observed gaps
  • SOC 2 / ISO 27001 baseline2 observed gaps

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

Abox.com74.112.186.157
AAAAbox.com2620:117:bff0:12d::
MXbox.com10 mxa-00172704.gslb.pphosted.com | 10 mxb-00172704.gslb.pphosted.com
NSbox.comdns1.p09.nsone.net | dns2.p09.nsone.net | dns3.p09.nsone.net | dns4.p09.nsone.net | ns01.box-ns.com | ns02.box-ns.com | ns03.box-ns.com | ns04.box-ns.com
TXTbox.comMS=ms77284419 | 00D600000007C2q=1TBUT00000000xh | _ekctc4i0t2i82uxe4xittvln2jdo1ns | asv=62e1f7ac21943b00bec6d263491f5afd | apple-domain-verification=Q6ZbrwNpV5Nf6mMX | status-page-domain-verification=pg69mfwsg50n | docusign=c74e9bc1-e686-4549-a027-502ac2647988 | 1password-site-verification=UBIBTNGWFJBIJPPKGYJZQ4XNLA | amazonses:w3BTGefFeXuqvvmfdFuGriN4u5DrNP9Ru7y6AqDfZ+Q= | openai-domain-verification=dv-3pcNwVWmbuCazHeb2Hy9j26y | detectify-verification=34418ef6d428fa589e0242009de86e7d | mongodb-site-verification=a29HTYZEP557j7IUIaaUOzZm5HxbvY1a | mongodb-site-verification=iXfoWZuaZFu9OYf003LE2n1PZfF20zew | cursor-domain-verification-8n2hsc=a4pjEJLogybVKLzoKGqqNjMv2 | onetrust-domain-verification=a153d3509dff42aa954e04fa87e2ee91 | zoom-domain-verification=7741ebe2-17cb-41d6-b176-baf04b7705a6 | anthropic-domain-verification-ede8t0=p69vPv6cbVNPGb8gkr3h5QCes | logmein-verification-code=0acf05fe-c5b7-4ec9-9a9b-be3b191c7834 | pendo-domain-verification=b9ef9d71-a87e-4adb-a96d-51c73f2d26d3 | 5d9f07a12f786083f86c9582e5aff6e3bb335b0f2fc387f0af9e76eb8e68b76e | google-site-verification=AZmX_1q4RIqFdW_0j9dt63wGv_eehN7F555UnDfdGKk | google-site-verification=A_i8cN9XRXZtfSZjRNN7JHPA_8H-D0uY9QqNTOY7Las | google-site-verification=Dg1l9TgAq2lCkemvxJbiGH4wLxpkR10utcxOS9nt02o | google-site-verification=LaeRMxQr903bnLCO_lQ1AmTBc-oKWTJGU_BFeBXBcKw | google-site-verification=OPFD055ic5Z0Twt9Oh3Vc7JEzK6W0ZdlwJ1w49KnLAQ | google-site-verification=e8_0EdcAu3Qp7xMpq10w8jg0a0thepvNICHOr3LMZS0 | google-site-verification=ixberGbEpG-6o-WjOsKq3G8vwYzfJPk4-grr8JIiEy4 | drift-domain-verification=69ba9345c1274754f39ffcd36db7f7c18a1fc04b98b234acc2575cfcd3ac5baf | atlassian-domain-verification=RBsyK96btDKk5ogVdtgwr3DUdfWI2BMzn1vpPsdGEXEtYDvXzsTdM7ubFx7HVhZH | paloaltonetworks-site-verification=e69cd908157ca263aebd6aa724d6f40903c62a390edeae2ffcb223a286e81ee0 | v=spf1 ip4:74.112.184.0/22 ip4:107.152.16.0/20 ip4:204.14.232.0/22 ip4:202.129.242.0/25 ip4:34.211.27.153 ip4:54.70.65.68 include:_spf.google.com include:sendgrid.net include:_spf.mxhero.com include:_spf.q4press.com include:stspg-customer.com include:5608010.spf08.hubspotemail.net ~all
TXT_dmarc.box.comv=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:reports@dmarc.cyber.dhs.gov; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
CAAbox.com0 issue "digicert.com" | 0 issue "www.digicert.com"
DSbox.com48553 13 2 61b5bbf45317bade560d8a4e1d3e512a1d98be7d825b083aade28cf62d5915cf
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