Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=ultikits.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
September 23, 2026
Valid Until
December 22, 2026 72 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
58:BE:05:A4:ED:AF:CC:43:72:32:59:11:BF:78:A9:8D:A5:63:63:BB:0E:DC:31:BE:66:EA:39:06:CF:CA:45:9C
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
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
letsencrypt.org pki.goog ; cansignhttpexchanges=yes ssl.com comodoca.com digicert.com ; cansignhttpexchanges=yes
Wildcard CAs
comodoca.com digicert.com ; cansignhttpexchanges=yes letsencrypt.org pki.goog ; cansignhttpexchanges=yes ssl.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 5 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts

Subject Alternative Names

1 domain