SSL check results of guadalupi.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for guadalupi.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 Sun, 25 Oct 2020 19:14:19 +0000

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

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

/mailservers/guadalupi.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.igordesign.com
45.79.172.96
5
supported
igordesign.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
28 s
mta.igordesign.com
93.41.134.167
10
supported
igordesign.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mx1.guadalupi.com
79.60.222.61
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=igordesign.com

Certificate chain
Subject
Common Name (CN)
  • igordesign.com
Alternative Names
  • *.guadalupi.com
  • *.igordesign.com
  • *.winzoz.com
  • guadalupi.com
  • igordesign.com
  • winzoz.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-19
Not valid after
2021-01-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
40:7B:5C:3A:AA:AC:D6:A1:46:20:93:91:F7:6A:A6:BE:A8:91:06:0B:79:1E:F6:F8:2B:60:21:31:D9:8F:E8:B5
SHA1
AA:33:52:BE:39:70:37:63:5C:C1:5B:51:E9:CC:BC:62:84:3E:7B:C7
X509v3 extensions
subjectKeyIdentifier
  • 59:0C:6D:0B:E2:FB:9C:9B:36:ED:1E:1C:6D:EA:48:EA:59:AF:48:41
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Oct 19 17:06:14.543 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B1:CD:A1:3F:31:9C:4B:0B:61:80:A6:
  • 38:5C:E8:B6:DD:8A:9C:01:CC:B6:E8:5E:B3:CC:2D:DB:
  • 3F:AB:6F:F6:A6:02:21:00:DA:49:9F:1E:21:2A:71:86:
  • 97:C9:60:47:C1:03:B5:7B:1C:6D:81:6D:59:C4:C7:6D:
  • B8:CD:D5:0E:77:1A:8F:7D
  • 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 : Oct 19 17:06:14.544 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:17:8D:4B:BD:FF:D5:0A:A2:34:BB:A0:
  • 43:D5:BE:2C:3B:5F:3E:E2:99:C6:2B:2B:43:07:B8:7F:
  • C4:31:E7:23:02:21:00:F1:1B:F6:2C:71:29:C2:B6:07:
  • E7:90:0A:B2:31:35:F6:60:D9:5D:A8:DC:F3:61:84:E9:
  • CC:49:DE:5A:EF:36:2E