DNS Gurus
Open Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=Sunnyvale, O=Fortinet, Inc., CN=*.fortimailcloud.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
July 23, 2025
Valid Until
August 21, 2026 257 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E9:6F:22:A3:98:96:9A:A0:36:93:B4:CF:AB:99:1F:D4:C1:16:4E:82:8C:6B:E0:1C:8D:CC:62:6C:0B:DD:30:16
Alternative Names
12 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
script-src; object-src; frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • • No CAA records configured - any CA can issue certificates
Recommendations
  • • Implement CAA records to restrict which CAs can issue certificates for your domain
  • • This adds an extra layer of security against unauthorized certificate issuance
  • • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • • Consider adding 'iodef' record to receive security incident reports