DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 4
Let's Encrypt logo Let's Encrypt Active incidents Google Fonts logo Google Fonts Google reCAPTCHA logo Google reCAPTCHA Google Search logo Google Search

Certificate Information

Subject
CN=api.gitlabhost.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 20, 2026
Valid Until
June 18, 2026 36 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
97:0B:F7:9B:0C:65:19:C5:2D:6C:BB:35:E9:EE:6D:EF:AD:D6:0E:09:70:20:A0:16:F7:A6:15:2E:AB:D0:36:1D
Alternative Names
2 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
Missing
Not configured
Content-Security-Policy
Google reCAPTCHA logo
Good
font-src; default-src; frame-ancestors; +6 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
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
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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

Subject Alternative Names

2 domains
api.gitlabhost.com app.gitlabhost.com