SSL-Tools

SSL check results of pgpmail.me

NEW You can also bulk check multiple servers.

Discover if the mail servers for pgpmail.me 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, 31 Aug 2026 00:30:30 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.pgpmail.me
2001:41d0:801:2000::f97
 10
supported
mail.pgpmail.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.pgpmail.me
51.38.64.217
 10
supported
mail.pgpmail.me
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 @pgpmail.me address so far. Test mail delivery

Certificates

First seen at:

CN=mail.pgpmail.me

Certificate chain
  • mail.pgpmail.me
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.pgpmail.me
Alternative Names
  • mail.pgpmail.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-25
Not valid after
2026-11-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
06:8D:F3:E2:6D:97:EB:00:62:F3:3E:64:1C:83:D9:DE:54:F1:9C:81:BB:FC:73:51:E4:08:80:79:74:B8:5D:FA
SHA1
68:22:60:79:F4:86:AD:EF:4B:A6:14:C7:55:4C:1C:C3:BB:26:C6:00
X509v3 extensions
subjectKeyIdentifier
  • CD:8F:5C:70:6E:74:5A:73:47:52:33:18:76:2B:7D:E5:B1:CA:1C:DB
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/109.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : Aug 25 21:00:18.670 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:47:3B:5D:5A:7B:5A:05:B2:19:BF:49:CE:
  • 3A:97:74:98:33:B4:F4:D7:8C:47:14:33:AE:55:9C:6B:
  • 2E:5E:34:61:02:21:00:CF:BA:39:09:EB:82:59:DC:B5:
  • 36:3E:29:A0:7F:06:38:6C:0C:95:29:5E:CC:AD:FF:97:
  • CE:81:BB:8A:20:95:3D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Aug 25 21:00:19.364 2026 GMT
  • Extensions: 00:00:05:00:38:CB:91:6D
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1F:42:6C:51:56:01:E9:64:50:6D:18:3F:
  • B5:03:08:06:BA:A1:AC:53:05:04:D2:EA:2B:EA:71:B4:
  • 8A:3A:7A:24:02:21:00:F6:28:B3:76:30:53:FF:FA:84:
  • B2:8F:7E:E4:A6:34:3F:A8:C6:E8:9C:30:6F:26:58:D6:
  • 05:15:96:EF:33:DF:58