SSL-Tools

SSL check results of allenspecialty.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for allenspecialty.com 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 Thu, 03 Oct 2024 16:48:46 +0000

We can not guarantee a secure connection to the mailservers of allenspecialty.com!

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

/mailservers/allenspecialty.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @allenspecialty.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.allen.enterprises
2401:c080:1400:67fe:5400:4ff:fe40:2c4
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.allen.enterprises
149.28.152.59
 10
supported
mail.allen.enterprises
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
22 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.allen.enterprises

Certificate chain
  • mail.allen.enterprises
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.allen.enterprises
Alternative Names
  • mail.allen.enterprises
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-30
Not valid after
2024-12-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FB:1B:1C:A3:23:6E:06:48:96:3A:A6:AB:B1:4A:44:32:3C:66:99:0E:2E:56:9C:2C:B3:3B:A2:EE:4D:52:FB:92
SHA1
C9:E4:EE:8D:A8:18:04:75:ED:66:38:A1:25:D8:07:22:D6:C2:D0:01
X509v3 extensions
subjectKeyIdentifier
  • 1E:19:FB:D9:C8:C1:3C:84:AC:D0:F7:67:49:C2:45:3F:1E:C1:21:85
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.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 : Sep 30 23:47:40.500 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:32:CB:78:BB:EF:4E:02:93:F3:C5:
  • 89:51:12:5B:8D:AE:ED:4D:3C:F1:82:D6:2A:29:2C:EA:
  • 63:44:10:C7:A1:02:20:43:BF:89:BD:30:8D:99:3F:F2:
  • BB:36:F4:37:9A:81:68:70:71:E4:4A:CC:E5:57:24:94:
  • E3:61:FC:44:34:03:A9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Sep 30 23:47:40.626 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3A:99:EB:92:E2:F1:9A:06:20:21:2D:A3:
  • 3C:DC:1E:33:BD:41:1D:46:36:D0:A9:76:FC:6B:90:7A:
  • 4C:48:B3:05:02:20:21:3B:90:53:51:84:11:30:5F:B8:
  • D5:4D:E2:DA:BB:FB:AB:86:B5:0D:1A:F7:54:BB:10:CE:
  • FF:04:6E:68:B6:49