SSL check results of operationgadget.com

NEW You can also bulk check multiple servers.

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

Report created Mon, 01 Jun 2020 00:30:27 +0000

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

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

/mailservers/operationgadget.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.operationgadget.com
2600:3c03::f03c:91ff:fe59:2794
Results incomplete
5 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.operationgadget.com
45.79.188.252
5
supported
after6services.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s

Outgoing Mails

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

Certificates

First seen at:

CN=after6services.com

Certificate chain
Subject
Common Name (CN)
  • after6services.com
Alternative Names
  • after6services.com
  • lin1.after6services.com
  • www.after6services.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-04-24
Not valid after
2020-07-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1D:F5:88:B9:94:C8:D4:AC:BC:3C:A8:25:42:02:57:BA:D0:D4:3B:AD:92:C4:63:16:88:C1:0D:34:E5:BC:D5:22
SHA1
64:B8:FD:BC:3C:50:BD:BF:D9:F0:80:33:96:54:30:A2:76:8B:CE:E9
X509v3 extensions
subjectKeyIdentifier
  • CE:CE:2C:D0:5A:38:BF:6F:0C:C8:E6:DE:C9:9C:EE:54:60:D2:03:E3
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : Apr 24 23:40:43.347 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:10:47:97:E9:3B:5E:03:55:03:BB:2F:B8:
  • 4C:C6:95:D5:88:38:21:B6:E1:8A:01:3B:B6:8F:21:F7:
  • C0:7C:57:8B:02:20:6B:0B:38:C3:D1:7B:60:5C:C1:5E:
  • A3:41:70:E9:1C:D3:C2:87:8A:5C:5B:A0:D0:D6:B7:45:
  • D6:AB:03:BA:49:75
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : Apr 24 23:40:43.374 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4B:00:DA:90:2F:8A:8F:41:D4:E4:2B:95:
  • 1A:F6:CD:95:7D:1E:46:50:74:4B:21:35:98:96:63:56:
  • 9B:7C:46:14:02:21:00:E6:A2:A8:B0:C6:05:16:90:65:
  • D2:34:D3:B6:1B:27:63:3C:19:B2:7D:78:84:56:F6:63:
  • 35:96:A1:01:AD:12:26