SSL-Tools

SSL check results of xervers.pt

NEW You can also bulk check multiple servers.

Discover if the mail servers for xervers.pt 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, 04 Oct 2024 00:30:24 +0000

The mailservers of xervers.pt can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @xervers.pt addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.xervers.pt
2a0e:bc00::185:219:128:254
 10
supported
xervers.pt
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mail.xervers.pt
185.219.128.254
 10
supported
xervers.pt
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=xervers.pt

Certificate chain
  • xervers.pt
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • xervers.pt
Alternative Names
  • ftp.xervers.pt
  • hrdesk.xervers.pt
  • mail.xervers.pt
  • pop.xervers.pt
  • smtp.xervers.pt
  • support.xervers.pt
  • www.xervers.pt
  • xervers.pt
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
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
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7E:97:85:5C:C9:D0:1B:5F:43:24:AA:A4:69:19:63:C1:B7:C4:2F:FE:C2:73:BA:20:90:99:09:D0:80:C4:44:DB
SHA1
59:BA:17:7E:B8:FD:52:C2:70:7E:FC:15:EF:FC:47:A2:83:67:DB:E5
X509v3 extensions
subjectKeyIdentifier
  • 5E:77:0E:58:0D:52:30:62:99:9E:A8:FB:3F:62:9D:8A:D9:97:0C:60
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 14:26:29.010 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8F:AC:15:62:60:A2:71:9D:9D:C7:BB:
  • 4C:2D:52:77:47:A2:18:65:70:EA:69:8C:7C:A5:E8:82:
  • 2E:AF:A1:3E:76:02:21:00:91:05:A9:C7:69:97:F0:87:
  • E5:40:AD:4C:14:B5:B0:BC:8B:1E:33:E6:08:EC:B1:35:
  • 43:A8:F5:F5:5B:81:8A:CA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 30 14:26:29.017 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FD:E4:2E:E3:FB:A6:E0:AF:21:13:F2:
  • 42:B9:9F:5F:4D:AA:85:7A:54:FC:B2:E4:92:23:5B:31:
  • 40:FC:8E:2D:FB:02:20:0F:4A:9F:59:34:4B:CA:FD:E3:
  • 63:40:08:1A:4E:EF:81:F8:D3:C1:8E:D4:A5:35:15:2E:
  • C9:BA:3F:0D:68:98:3F