SSL-Tools

SSL check results of preciselyrightonline.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for preciselyrightonline.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 Wed, 31 May 2023 19:22:22 +0000

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

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

/mailservers/preciselyrightonline.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
one.mxroute.com
49.12.120.198
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
one-relay.mxroute.com
49.12.120.198
 20
supported
sunfire.mxrouting.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=sunfire.mxrouting.net

Certificate chain
  • sunfire.mxrouting.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • sunfire.mxrouting.net
Alternative Names
  • sunfire.mxrouting.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-04-12
Not valid after
2023-07-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
98:A0:03:A2:BA:28:AA:73:C9:06:CB:6B:67:5B:3F:5E:47:0E:00:D6:08:3D:11:29:EC:C8:EE:F3:9C:BB:B0:CF
SHA1
2C:12:FE:58:00:0B:67:0B:7F:3C:F8:BB:0A:6C:ED:CF:20:AE:4F:4A
X509v3 extensions
subjectKeyIdentifier
  • BB:FF:C3:A1:4A:2F:BE:D9:B1:26:86:24:44:31:DE:12:E0:83:9F:7D
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Apr 12 14:59:16.365 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9F:A4:12:82:12:AC:F4:7D:C4:2A:07:
  • 84:AD:87:10:E8:9F:E3:20:A2:04:72:1B:FE:93:EF:90:
  • 26:97:77:42:9E:02:21:00:BF:A7:6B:F4:AB:F6:F6:4C:
  • 47:AD:F9:22:93:4D:DB:8D:2C:F2:06:B1:48:CA:97:A6:
  • B5:D7:4E:35:B8:4A:DB:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Apr 12 14:59:16.341 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:69:87:7C:11:94:49:2C:12:FB:5F:84:2F:
  • 77:C7:4E:CA:5B:BA:6A:47:4C:BA:E3:0D:1A:FE:6D:CB:
  • FA:8B:26:9B:02:20:2D:02:13:1A:5F:FA:16:57:7A:D0:
  • 7C:F4:23:22:EF:D4:C0:80:56:4B:44:3E:D9:9F:A5:00:
  • 2C:47:5F:CF:90:8E