SSL-Tools

SSL check results of alammotortrade.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for alammotortrade.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 Fri, 07 Feb 2025 01:31:07 +0000

We can not guarantee a secure connection to the mailservers of alammotortrade.uk!

Please contact the operator of alammotortrade.uk and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/alammotortrade.uk

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
alammotortrade.uk
2604:9a00:2100:a105:1::1
Results incomplete
5
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
21 s
alammotortrade.uk
198.251.89.82
 5
supported
*.alammotortrade.uk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @alammotortrade.uk address so far. Test mail delivery

Certificates

First seen at:

CN=*.alammotortrade.uk

Certificate chain
  • *.alammotortrade.uk
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.alammotortrade.uk
Alternative Names
  • *.alammotortrade.uk
  • alammotortrade.uk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-11-30
Not valid after
2025-02-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
35:11:26:43:3F:15:46:3B:5A:25:E3:F7:A5:E3:0C:88:E0:84:C7:6A:6C:EC:DE:74:C0:DE:0B:F9:8E:FA:76:3D
SHA1
B0:01:DF:6F:99:37:C8:19:2F:F2:0E:02:6D:32:5E:45:32:8E:30:05
X509v3 extensions
subjectKeyIdentifier
  • 13:30:BD:18:19:4F:E8:2C:E8:B4:6C:20:D8:FF:97:D8:DF:6F:2C:30
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Nov 30 18:55:54.878 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C0:0C:76:8B:38:B6:CA:69:F1:8C:ED:
  • 01:D4:1C:74:32:DB:DA:33:13:D3:3D:C3:8E:CE:58:7E:
  • 66:69:89:C0:2A:02:20:0D:C4:3D:BF:17:44:B6:07:21:
  • A3:DD:88:4C:4F:A6:F0:DC:E8:FB:50:F0:DE:81:B8:37:
  • D3:5B:7E:FB:53:9E:48
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Nov 30 18:55:54.895 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BE:4B:FB:D7:3E:BC:27:F3:98:A5:48:
  • 95:BC:C8:1A:42:D4:54:D6:47:C1:F8:C3:2A:C4:36:C4:
  • 96:9D:5C:46:3D:02:20:48:A9:14:59:A5:DD:52:5C:FD:
  • 94:1E:B6:C2:4A:B9:CC:07:B1:E3:22:11:B2:CC:7F:02:
  • 4A:24:FE:D0:95:A5:5D