SSL check results of owner.pw

NEW You can also bulk check multiple servers.

Discover if the mail servers for owner.pw 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

Report created Wed, 14 Apr 2021 14:42:03 +0000

We can not guarantee a secure connection to the mailservers of owner.pw!

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

/mailservers/owner.pw

Servers

Incoming Mails

These servers are responsible for incoming mails to @owner.pw addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
owner.pw
2400:8500:1801:413:118:27:27:27
10
supported
owner.pw
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
owner.pw
118.27.27.27
10
supported
owner.pw
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
mx.unit01.paasmail.tyo1.conoha.io
157.7.93.128
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=owner.pw

Certificate chain
  • owner.pw
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • owner.pw
Alternative Names
  • cloud.owner.pw
  • owner.pw
  • www.owner.pw
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-20
Not valid after
2021-05-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B2:D4:2F:09:B5:15:80:71:7E:8F:5F:51:83:07:8A:D5:A5:A0:86:77:9F:E1:01:25:85:A0:4D:06:BA:05:3E:0D
SHA1
63:59:E8:20:78:49:C1:E8:5B:E9:3A:67:14:A3:28:CE:ED:4E:9C:EB
X509v3 extensions
subjectKeyIdentifier
  • 16:18:F4:E4:19:D8:43:80:A2:CA:83:FD:08:31:8A:AA:0D:BB:95:C8
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 : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Feb 20 06:34:21.244 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DD:6F:EC:23:91:1F:4F:CF:5E:C9:08:
  • F5:B2:20:09:6A:61:C6:F2:32:23:8F:50:34:A0:B9:0B:
  • 73:A3:AF:FF:E2:02:20:1E:D5:CB:97:D1:F4:92:58:41:
  • 74:55:8C:11:CE:7D:DE:99:1D:BF:A9:C0:E8:7C:15:E7:
  • 67:68:72:DF:BA:2B:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Feb 20 06:34:21.713 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:10:88:EA:24:86:36:7F:DF:E1:9A:31:D5:
  • 42:4D:3C:70:E9:B0:2F:A9:89:6C:41:92:8A:F1:EC:91:
  • 2B:CA:DF:38:02:21:00:A8:7C:D1:E0:82:95:65:AF:C5:
  • 9E:AB:CA:38:3C:58:65:84:99:76:7F:B1:CB:E6:EF:9A:
  • 57:50:3C:62:11:07:42