SSL-Tools

SSL check results of yahoo.co.in

NEW You can also bulk check multiple servers.

Discover if the mail servers for yahoo.co.in 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 Tue, 27 Oct 2020 05:54:38 +0000

The mailservers of yahoo.co.in can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @yahoo.co.in addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx-apac.mail.gm0.yahoodns.net
106.10.248.73
 10
supported
*.am0.yahoodns.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s
mx-apac.mail.gm0.yahoodns.net
106.10.248.74
 10
supported
*.am0.yahoodns.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

We have not received any emails from a @yahoo.co.in address so far. Test mail delivery

Certificates

First seen at:

CN=*.am0.yahoodns.net,O=Oath Inc,L=Sunnyvale,ST=California,C=US

Certificate chain
Subject
Country (C)
  • US
State (ST)
  • California
Locality (L)
  • Sunnyvale
Organization (O)
  • Oath Inc
Common Name (CN)
  • *.am0.yahoodns.net
Alternative Names
  • *.am0.yahoodns.net
  • *.mail.am0.yahoodns.net
  • *.sbcglobal.am0.yahoodns.net
  • *.mail.gm0.yahoodns.net
  • *.gm0.yahoodns.net
  • *.biz.mail.yahoo.com
  • *.bullet.am0.yahoodns.net
Issuer
Country (C)
  • US
Organization (O)
  • DigiCert Inc
Organizational Unit (OU)
  • www.digicert.com
Common Name (CN)
  • DigiCert SHA2 High Assurance Server CA
validity period
Not valid before
2020-08-17
Not valid after
2020-11-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
72:FB:8F:51:71:01:B1:1D:80:C9:51:FF:C7:8C:F9:B4:EB:CE:D3:AC:E6:89:69:40:FE:F5:F8:30:2E:F4:63:2F
SHA1
E4:8C:7A:F9:C7:5B:1C:DA:26:39:02:6D:6B:71:B8:F9:39:57:F8:3B
X509v3 extensions
authorityKeyIdentifier
  • keyid:51:68:FF:90:AF:02:07:75:3C:CC:D9:65:64:62:A2:12:B8:59:72:3B
subjectKeyIdentifier
  • B4:FD:20:62:4F:A5:0A:C2:D8:49:30:98:15:02:34:56:1E:1B:B4:BB
crlDistributionPoints
  • Full Name:
  • URI:http://crl3.digicert.com/sha2-ha-server-g6.crl
  • Full Name:
  • URI:http://crl4.digicert.com/sha2-ha-server-g6.crl
certificatePolicies
  • Policy: 2.16.840.1.114412.1.1
  • CPS: https://www.digicert.com/CPS
  • Policy: 2.23.140.1.2.2
authorityInfoAccess
  • OCSP - URI:http://ocsp.digicert.com
  • CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt
ct_precert_scts
  • 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 : Aug 17 15:55:35.258 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:44:D5:06:B4:47:88:80:50:2A:B7:10:CF:
  • A5:23:96:0E:F6:F3:88:F0:3D:C8:44:CB:3C:B8:99:BC:
  • 38:CE:9D:C9:02:20:79:37:79:8F:B5:F3:A8:76:82:85:
  • A4:80:51:F0:8B:8C:AC:C9:EF:75:3A:06:E8:EB:EA:15:
  • 09:12:01:71:7C:30
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : Aug 17 15:55:35.234 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5A:AC:46:B6:A7:91:D7:9B:BD:BB:85:95:
  • 7D:5B:11:B4:8B:FB:41:12:17:4B:FE:FD:EC:78:27:1A:
  • 5B:70:36:62:02:20:2C:69:99:00:93:CE:B0:0D:2A:07:
  • 2B:B9:B7:19:92:4E:AE:B4:5D:7C:BF:7D:98:68:A9:FB:
  • 09:4B:5B:A9:D5:97