SSL Report: beyadify.ir (185.208.173.3)
Assessed on:  Tue, 02 Sep 2025 08:54:04 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
A
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server supports TLS 1.3.  MORE INFO »
Certificate #1: RSA 4096 bits (SHA256withRSA)
Server Key and Certificate #1
Subject beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=
Common names beyadify.ir
Alternative names *.beyadify.ir beyadify.ir
Serial Number 051b340d8643e810368871844cd756549ba3
Valid from Mon, 18 Aug 2025 03:17:01 UTC
Valid until Sun, 16 Nov 2025 03:17:00 UTC (expires in 2 months and 13 days)
Key RSA 4096 bits (e 65537)
Weak key (Debian) No
Issuer R10
AIA: http://r10.i.lencr.org/
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency Yes (certificate)
OCSP Must Staple No
Revocation information CRL
CRL: http://r10.c.lencr.org/36.crl
Revocation status Good (not revoked)
DNS CAA No (more info)
Trusted Yes
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 3 (4371 bytes)
Chain issues Incorrect order, Extra certs
#2
Subject beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=
Valid until Sun, 16 Nov 2025 03:17:00 UTC (expires in 2 months and 13 days)
Key RSA 4096 bits (e 65537)
Issuer R10
Signature algorithm SHA256withRSA
#3
Subject R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=
Valid until Fri, 12 Mar 2027 23:59:59 UTC (expires in 1 year and 6 months)
Key RSA 2048 bits (e 65537)
Issuer ISRG Root X1
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Trusted
1 Sent by server beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Trusted
1 Sent by server beyadify.ir
Fingerprint SHA256: 4ea34f7c1d3f5cfe66c6f169948b7380e5221961c713c525f5f4c7629d34ee25
Pin SHA256: 89nYzuESWw4k0tdo4db0+neM2Wql3m8yQ2dWvz0dsR8=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server R10
Fingerprint SHA256: 9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
Pin SHA256: K7rZOrXHknnsEhUH8nLL4MZkejquUuIvOIr6tCa0rbo=

RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA

Click here to expand

Configuration
Protocols
TLS 1.3 Yes
TLS 1.2 No
TLS 1.1 No
TLS 1.0 No
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.3 (suites in server-preferred order)
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_CHACHA20_POLY1305_SHA256 (0x1303)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_AES_128_GCM_SHA256 (0x1301)   ECDH x25519 (eq. 3072 bits RSA)   FS 128


Handshake Simulation
Android 8.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Android 9.0 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Chrome 69 / Win 7  R Server sent fatal alert: protocol_version
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Firefox 62 / Win 7  R Server sent fatal alert: protocol_version
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Java 11.0.3 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 12.0.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.0k  R Server sent fatal alert: protocol_version
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Android 4.4.2 Protocol mismatch (not simulated)
Android 5.0.0 Protocol mismatch (not simulated)
Android 6.0 Protocol mismatch (not simulated)
Android 7.0 Protocol mismatch (not simulated)
Android 8.0 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
BingPreview Jan 2015 Protocol mismatch (not simulated)
Chrome 49 / XP SP3 Protocol mismatch (not simulated)
Firefox 31.3.0 ESR / Win 7 Protocol mismatch (not simulated)
Firefox 47 / Win 7  R Protocol mismatch (not simulated)
Firefox 49 / XP SP3 Protocol mismatch (not simulated)
Googlebot Feb 2018 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 11 / Win 7  R Protocol mismatch (not simulated)
IE 11 / Win 8.1  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
IE 11 / Win Phone 8.1  R Protocol mismatch (not simulated)
IE 11 / Win Phone 8.1 Update  R Protocol mismatch (not simulated)
IE 11 / Win 10  R Protocol mismatch (not simulated)
Edge 15 / Win 10  R Protocol mismatch (not simulated)
Edge 16 / Win 10  R Protocol mismatch (not simulated)
Edge 18 / Win 10  R Protocol mismatch (not simulated)
Edge 13 / Win Phone 10  R Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
Java 8u161 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
OpenSSL 1.0.1l  R Protocol mismatch (not simulated)
OpenSSL 1.0.2s  R Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6 / iOS 6.0.1 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R Protocol mismatch (not simulated)
Safari 7 / iOS 7.1  R Protocol mismatch (not simulated)
Safari 7 / OS X 10.9  R Protocol mismatch (not simulated)
Safari 8 / iOS 8.4  R Protocol mismatch (not simulated)
Safari 8 / OS X 10.10  R Protocol mismatch (not simulated)
Safari 9 / iOS 9  R Protocol mismatch (not simulated)
Safari 9 / OS X 10.11  R Protocol mismatch (not simulated)
Safari 10 / iOS 10  R Protocol mismatch (not simulated)
Safari 10 / OS X 10.12  R Protocol mismatch (not simulated)
Apple ATS 9 / iOS 9  R Protocol mismatch (not simulated)
Yahoo Slurp Jan 2015 Protocol mismatch (not simulated)
YandexBot Jan 2015 Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN Yes   h2 http/1.1
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) Yes   TOO SHORT (less than 180 days)
max-age=50;preload
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Supported Named Groups x25519, secp256r1, secp384r1, secp521r1 (server preferred order)
SSL 2 handshake compatibility No
0-RTT enabled No


HTTP Requests
1 https://beyadify.ir/  (HTTP/1.1 200 OK)
1
Date Tue, 02 Sep 2025 08:53:47 GMT
Content-Type text/html; charset=utf-8
Transfer-Encoding chunked
Connection close
Strict-Transport-Security max-age=50;preload
server WCDN 3.5.1
X-Powered-By Next.js
Cache-Control private, no-cache, no-store, max-age=0, must-revalidate
Vary Accept-Encoding
wcdn-edge 10.0.0.100
wcdn-edge-id 9733646
wcdn-cache-policy SMART
wcdn-rayid W9733646T1756803226R25150
wcdn-cacheid 72cb0c4fa4be0f96dd02dea9fd38b543dbcbda15e5240c1002414e6837d9acbd
wcdn-nfc-reason ContentLength_ResponseHeader
wcdn-status NFC
wcdn-delivery-duration 0
wcdn-hosting-waiting-duration 1302
wcdn-connection-duration 708
wcdn-total-duration 2010


Miscellaneous
Test date Tue, 02 Sep 2025 08:53:41 UTC
Test duration 22.856 seconds
HTTP status code 200
HTTP server signature WCDN 3.5.1
Server hostname -


SSL Report v2.4.1