SSL check results of arrishq.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for arrishq.net 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 Tue, 30 Mar 2021 12:04:09 +0000

The mailservers of arrishq.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @arrishq.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail1.arrishq.net
178.63.103.215
10
supported
*.arrishq.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail2.arrishq.net
94.242.59.6
20
supported
*.arrishq.net
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.arrishq.net

Certificate chain
  • *.arrishq.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • *.arrishq.net
Alternative Names
  • *.arrishq.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-27
Not valid after
2021-06-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
22:E7:E0:F5:DD:AB:A7:37:A1:60:B6:EA:56:55:01:91:3C:8E:25:4C:9B:CB:4D:58:7B:EB:08:3D:18:01:21:F5
SHA1
DD:EB:B1:97:57:8A:C0:E7:44:B2:DE:38:67:8A:3F:EF:C0:C5:79:A2
X509v3 extensions
subjectKeyIdentifier
  • 44:C6:7E:6C:3B:49:C0:EA:70:CE:88:86:20:B5:5E:7D:79:DD:9B:1A
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Mar 27 03:17:45.954 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5D:B4:36:48:98:73:34:AF:C1:0C:F7:16:
  • 7E:FB:61:36:C2:EB:60:09:48:55:95:CF:81:3C:64:93:
  • 69:40:90:5C:02:21:00:87:BD:85:E6:3A:99:32:85:FE:
  • 68:79:50:03:BA:9B:0A:E0:4C:DA:EB:A7:2B:1F:68:FC:
  • 9A:02:4A:5C:72:B3:E9
  • 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 : Mar 27 03:17:45.955 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2D:88:FD:29:C9:0F:00:58:C8:9A:1A:E4:
  • CE:59:E7:E3:55:45:1C:17:8D:71:D8:BD:51:46:21:64:
  • 75:77:E8:95:02:21:00:CC:D5:0D:7E:40:D2:6F:43:DB:
  • B3:E5:F7:87:56:46:B2:3A:F9:C2:70:81:55:3E:0D:10:
  • 90:7F:EB:88:2E:23:6F

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail1.arrishq.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mail2.arrishq.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid