SSL/TLS Analysis for git.karmakrafts.dev
Analyzed on November 02, 2025 at 13:51 UTC
Security Score
87
/
100
Certificate Information
Subject
CN=karmakrafts.dev
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 14, 2025
Valid Until
January 12, 2026
70 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
E2:8C:2E:A2:78:5C:BA:08:84:0E:4F:DA:EB:0C:5B:FD:0E:C2:5D:D5:1F:5E:22:EC:9D:07:D6:15:21:7D:16:0D
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
Weak
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
interest-cohort=()
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
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