SSL-Tools

SSL check results of rilynn.me.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for rilynn.me.uk 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 Sun, 28 Apr 2024 16:57:44 +0000

The mailservers of rilynn.me.uk can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rilynn.me.uk addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
rilynn.me.uk
90.155.73.34
 10
supported
rilynn.me.uk
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

We have received emails from these servers with @rilynn.me.uk sender addresses. Test mail delivery

Host TLS Version & Cipher
rilynn.me.uk (90.155.73.34)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=rilynn.me.uk

Certificate chain
  • rilynn.me.uk
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • rilynn.me.uk
Alternative Names
  • rilynn.me.uk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-28
Not valid after
2024-06-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DC:70:00:80:29:DF:DC:FF:F2:EC:98:16:1F:DE:91:9C:03:52:55:57:4F:F7:06:38:3C:9F:00:56:D0:FB:C3:5D
SHA1
1E:D9:F1:80:3E:4A:4C:FB:07:A0:B6:43:9E:19:F4:E1:84:FD:16:FD
X509v3 extensions
subjectKeyIdentifier
  • C2:3E:0A:F3:C5:15:AA:7B:BE:F0:20:5B:3A:A2:F8:F9:7C:3B:9A:A6
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 28 04:49:09.569 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C9:11:2E:E8:6B:88:82:91:D6:BA:4D:
  • 90:D9:0A:B7:ED:C7:9A:36:3E:6C:05:F8:73:6D:0E:35:
  • 70:EE:FE:59:5D:02:20:27:4D:05:86:AD:64:E1:7E:B3:
  • F9:E4:4E:8B:52:26:37:EF:10:9C:56:55:55:34:DB:E7:
  • 30:3D:53:3E:80:26:B8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 28 04:49:09.564 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6B:C9:56:3E:F7:18:3D:58:61:DE:CE:47:
  • E7:E1:12:FC:BC:F9:AC:FB:24:91:3B:69:40:36:80:73:
  • 30:69:41:3F:02:20:4E:B8:85:48:A3:2F:52:B7:C4:F2:
  • B2:1D:5C:38:DF:08:20:DF:1E:D5:05:30:BE:1B:06:AB:
  • 01:5E:BA:EF:7F:01

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.rilynn.me.uk
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid