SSL-Tools

SSL check results of person.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for person.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 Sun, 06 Jul 2025 00:30:07 +0000

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

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

/mailservers/person.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mailerhost.net
5.161.133.13
Results incomplete
1
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mail.mailerhost.net
161.35.84.83
 1
supported
mail.mailerhost.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
26 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mailerhost.net

Certificate chain
  • mail.mailerhost.net
    • 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.mailerhost.net
Alternative Names
  • mail.mailerhost.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-06
Not valid after
2025-09-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B3:EB:1C:63:9C:B4:C4:F8:95:B1:F8:71:08:40:29:89:13:0A:1C:BB:A1:7D:87:15:3B:30:6E:F7:F9:8E:5F:DE
SHA1
91:77:3A:CA:5E:FD:A1:B0:6B:A6:C9:08:13:27:D5:5E:C8:72:33:95
X509v3 extensions
subjectKeyIdentifier
  • 12:BB:18:D1:26:D7:C3:F1:B9:91:AF:53:0E:E0:E0:05:9C:E0:F6:AD
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/21.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 6 11:53:36.045 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:F3:9C:7E:6B:4E:6C:D1:B2:2B:FD:BE:
  • B0:D0:D5:52:FC:66:AE:38:A4:A0:52:21:D6:A3:9B:3E:
  • 1F:E6:2C:6D:02:21:00:AD:93:46:0F:CB:71:91:8C:41:
  • F0:77:C0:4A:A1:F0:45:8A:10:2D:3B:FA:6A:8B:BF:A3:
  • EE:B6:79:43:4F:DD:00
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jun 6 11:53:36.050 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:74:90:72:28:CC:23:73:AB:57:28:42:87:
  • 35:28:FF:A8:6A:47:58:62:AF:1C:43:D2:0F:62:F0:F1:
  • A1:7C:DB:B8:02:20:35:C2:17:D1:6D:F2:99:F8:4F:6C:
  • E7:81:6A:07:02:18:F4:58:A8:38:95:EA:89:EA:2F:ED:
  • C5:BB:AC:8A:E2:28