Blog
Contact
Sign in
Scan complete
D
67/100
createit.com
Improved · E → D · +15
Compare
1 critical issue needs immediate attention.
16/16
checks
52
passed
finished
Scan timestamps
Created
Jul 20, 2026, 9:17 AM
Started
Jul 20, 2026, 9:17 AM
Finished
Jul 20, 2026, 9:18 AM
Updated
Jul 20, 2026, 9:17 AM
Export PDF
Re-scan
Findings by severity
71 results
1
Critical
6
High
5
Medium
7
Low
52
Pass
Report coverage
98.53%
24 skipped - these limit completeness.
24 skipped
All
95
Critical
1
High
6
Medium
5
Low
7
Pass
52
Skipped
24
Email
96%
Domain Alignment (DMARC)
Learn how it works
Info
6/7 pass
Domain Alignment (DMARC)
DMARC alignment is relaxed
The DMARC record allows relaxed identifier alignment for DKIM or SPF.
Low
Transport Encryption (SMTP TLS)
Learn how it works
Info
4/5 pass
Transport Encryption (SMTP TLS)
Some MX hosts negotiate TLS 1.2 instead of TLS 1.3
All MX hosts meet the minimum TLS 1.2 requirement, but at least one does not support TLS 1.3.
Low
Certificate Binding (DANE)
Learn how it works
Info
1/5 pass
Certificate Binding (DANE)
No MX host TLSA zone is protected by DNSSEC
None of the MX hosts have DNSSEC on their TLSA lookup zones. DANE SMTP cannot function without DNSSEC, as sending servers will ignore TLSA records from unsigned zones.
Critical
Transport Policy (MTA-STS)
Learn how it works
Info
1/6 pass
Transport Policy (MTA-STS)
MTA-STS DNS record is missing
The domain does not publish an MTA-STS TXT record, so sending servers cannot discover or enforce an MTA-STS policy.
High
TLS Reporting (TLS-RPT)
Learn how it works
Info
1/4 pass
TLS Reporting (TLS-RPT)
No TLS-RPT record found
The domain does not publish a TLS-RPT record. Sending servers cannot report TLS errors to this domain.
High
DNS
100%
DNS Integrity (DNSSEC)
Learn how it works
Info
0/7 pass
DNS Integrity (DNSSEC)
DNSSEC is not enabled
The parent zone does not publish a DS record for this domain.
Medium
DNS Health (Delegation & Exposure)
Learn how it works
Info
7/8 pass
DNS Health (Delegation & Exposure)
SOA serial does not use the recommended format
The SOA record is otherwise valid, but the serial number does not follow the recommended YYYYMMDDnn date format.
Low
CAA and Certificate Issuance Surface
Learn how it works
Info
4/6 pass
CAA and Certificate Issuance Surface
Certificate issuance is not pinned
The CAA records authorize a CA but do not restrict issuance to a specific account or validation method.
Low
CAA and Certificate Issuance Surface
No S/MIME issuance policy is published
The domain does not publish an issuemail CAA property, so any CA may issue S/MIME certificates for its email addresses; note that issue and issuewild do not restrict S/MIME issuance.
Low
TLS
100%
TLS Configuration
Learn how it works
Info
4/6 pass
TLS Configuration
Cipher suites without forward secrecy accepted
The server accepts one or more cipher suites using static RSA or static (EC)DH key exchange. If the server's private key is ever compromised, an attacker with recorded traffic can decrypt past sessions negotiated with these cipher suites.
Medium
TLS Configuration
TLS 1.3 early data (0-RTT) enabled
The server accepts 0-RTT early data. Requests sent as early data can be replayed by an attacker without detection unless the application implements its own anti-replay protection. This is safe only for idempotent requests.
Low
Web
100%
Disclosure Policy (security.txt)
Learn how it works
Info
0/4 pass
Disclosure Policy (security.txt)
security.txt is not present or not usable
The domain does not publish a usable security.txt file. Either both /.well-known/security.txt and /security.txt returned no file (404/401/403/410), or the location responded with HTTP 200 but non-text/plain content (typically an application page) or a body that is not valid UTF-8.
Medium
HTTP Security Headers
Learn how it works
Info
0/7 pass
HTTP Security Headers
HSTS is not enforced
The site does not send a usable Strict-Transport-Security header, so browsers do not automatically upgrade future requests to HTTPS.
High
HTTP Security Headers
Content-Security-Policy is not enforced
The site does not send an enforced Content-Security-Policy header, leaving no restriction on script execution, framing, or resource loading beyond what other headers provide.
High
HTTP Security Headers
Clickjacking protection is missing
The site does not restrict framing through CSP frame-ancestors or a usable X-Frame-Options value, so it can be embedded in a frame on any origin.
High
HTTP Security Headers
MIME sniffing is not disabled
The site does not send X-Content-Type-Options: nosniff, so browsers may MIME-sniff a response and interpret it as a different, potentially executable content type.
High
HTTP Security Headers
Referrer-Policy is not declared
The site does not send a Referrer-Policy header. Modern browsers default to a reasonably safe behavior, but the site does not explicitly guarantee it.
Medium
HTTP Security Headers
Permissions-Policy is missing or ineffective
The site either does not send a Permissions-Policy header, or the header only lists directives with a wildcard allowlist that does not restrict anything.
Medium
HTTP Security Headers
Server or framework version is exposed
The response discloses a specific server or framework version via the Server or X-Powered-By header, which can help an attacker match known vulnerabilities to the exact version.
Low
Feedback
