SSL-Tools

SSL check results of rough-riders-airsoft.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rough-riders-airsoft.de can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Mon, 21 Jul 2025 13:49:59 +0000

The mailservers of rough-riders-airsoft.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rough-riders-airsoft.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.nilsit.dev
2a01:4f8:211:509::2
 10
supported
*.nilsit.dev
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.nilsit.dev
148.251.178.182
 10
supported
*.nilsit.dev
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @rough-riders-airsoft.de address so far. Test mail delivery

Certificates

First seen at:

CN=*.nilsit.dev

Certificate chain
  • *.nilsit.dev
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.nilsit.dev
Alternative Names
  • *.nilsit.dev
  • nilsit.dev
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-01
Not valid after
2025-08-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
03:A2:F6:11:B0:0D:52:BD:D6:CF:06:C9:30:9F:5F:84:11:4C:66:84:FB:AF:E3:8B:BC:E0:73:7A:88:9B:2A:B0
SHA1
D3:89:14:F9:03:5F:71:E5:89:AA:14:E2:AE:C6:CB:B0:C9:03:67:16
X509v3 extensions
subjectKeyIdentifier
  • BE:79:8F:80:57:61:D1:0D:FE:76:86:91:D2:BF:60:8E:1E:AD:0A:47
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/21.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jun 1 19:53:39.808 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5B:28:E8:C2:87:C1:08:FF:4D:90:AC:42:
  • 57:72:9C:5E:F6:95:4E:5F:34:00:4E:75:6C:62:94:5A:
  • E7:3F:B4:DA:02:21:00:B6:1F:E2:30:99:56:4C:E3:30:
  • 42:01:78:2C:F4:D7:F5:93:22:15:78:FD:23:FE:66:7A:
  • 7C:72:58:08:3E:32:EE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 1 19:53:39.806 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B9:6A:28:BB:71:B1:DD:C4:C9:CD:56:
  • 03:EA:AA:C1:93:BB:E9:87:42:E2:D8:E9:74:57:7C:2B:
  • CF:A4:65:52:FF:02:21:00:B9:36:C3:5E:A0:81:B8:71:
  • 41:BE:AB:14:2E:CF:1A:F0:61:A0:4A:99:A6:39:8F:4A:
  • 88:E1:3F:D0:90:0E:8D:CA