DNS Gurus
Cached · just now
76/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
GlobalSign logo GlobalSign

Certificate Information

Subject
UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=1067746613494, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 82, 85>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 6, 77, 111, 115, 99, 111, 119>>}, C=RU, ST=Moscow, L=Moscow, UNKNOWN={:asn1_OPENTYPE, <<19, 38, 76, 101, 110, 105, 110, 103, 114, 97, 100, 115, 107, 121, 32, 112, 114, 111, 115, 112, 101, 107, 116, 44, 32, 55, 50, 32, 47, 32, 98, 117, 105, 108, 100, 105, 110, 103, 32, 51>>}, O=Registrar of domain names REG.RU LLC, CN=www.reg.ru
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R3 EV TLS CA 2025
Valid From
November 07, 2025
Valid Until
December 09, 2026 96 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
06:7B:34:65:88:F3:9A:6E:3D:73:2A:64:5C:03:87:9F:5A:95:BA:DF:45:E6:07:0B:F7:6A:56:5D:F7:ED:73:00
Alternative Names
5 domains

Security Configuration

TLS Protocols
TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • • TLS 1.1 is deprecated and should be disabled

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
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
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
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • 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