89/100 SECURITY SCORE

Certificate Information

Subject
CN=www.precisely.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 17, 2026
Valid Until
April 17, 2026 79 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
44:3C:5C:BF:5A:3E:AB:D4:5D:C3:1D:28:CE:4D:C2:4B:31:E4:71:48:9F:72:51:3C:E6:96:33:F5:C7:6F:EB:8E
Alternative Names

Security Configuration

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

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Basic
default-src; script-src; style-src; +6 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
autoplay=(self "https://*.qualified.com"), camera=(self "https://*.qualified.com"), gyroscope=(self "https://*.qualified.com"), magnetometer=(), microphone=(self "https://*.qualified.com"), payment=(), publickey-credentials-get=(), usb=(), browsing-topics=()
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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

Subject Alternative Names

1 domain