SSL Report:
xiaode.sg
(3.1.137.222)
Assessed on: Mon, 28 Jul 2025 04:40:25 UTC
| Clear cache
Summary
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's certificate is not trusted by major browsers. MORE INFO »
This site works only in browsers with SNI support.
This server supports TLS 1.3. MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.
MORE INFO »
Certificate #1: EC 256 bits (SHA384withECDSA)
|
Server Key and Certificate #1
|
|
| Subject |
xiaode.sg
Fingerprint SHA256: d23a6f48b8ce9e0a8cb4d67b7d1b20193cd7c4419200e7fd2bb389b96093e4dd Pin SHA256: nK+XUqYj54o5aal1gWavOamn8AucvnOX0p7FA42TcYU= |
| Common names | xiaode.sg |
| Alternative names | wdns.xiaode.sg www.xiaode.sg xiaode.sg |
| Serial Number | 065f85ee2204bd03da4a63c902ea16981c20 |
| Valid from | Sat, 31 May 2025 12:46:01 UTC |
| Valid until | Fri, 29 Aug 2025 12:46:00 UTC (expires in 1 month and 1 day) |
| Key | EC 256 bits |
| Weak key (Debian) | No |
| Issuer | E6
AIA: http://e6.i.lencr.org/ |
| Signature algorithm | SHA384withECDSA |
| Extended Validation | No |
| Certificate Transparency | Yes (certificate) |
| OCSP Must Staple | No |
| Revocation information |
CRL CRL: http://e6.c.lencr.org/33.crl |
| Revocation status | Good (not revoked) |
| DNS CAA | No (more info) |
| Trusted | Yes
Mozilla Apple Android Java Windows |
Certification Paths |
Certificate #2: EC 256 bits (SHA384withECDSA)
No SNI
|
Certification Paths |
Certificate #3: RSA 2048 bits (SHA256withRSA)
|
Server Key and Certificate #1
|
|
| Subject |
ip-172-26-6-38.ap-southeast-1.compute.internal
Fingerprint SHA256: 1ae9927c0add1c759e14d2c7bc5e3775e60ce6b0d13170fd305a29da062ca116 Pin SHA256: yLbmFWnNphGS88hDgjgY87cdjbAerXrtX/EyUdM5HZ8= |
| Common names | ip-172-26-6-38.ap-southeast-1.compute.internal |
| Alternative names | ip-172-26-6-38.ap-southeast-1.compute.internal MISMATCH |
| Serial Number | 4cf1b91ea9b6211c20efffd574c2f23c1ec8892b |
| Valid from | Fri, 21 Feb 2025 12:37:02 UTC |
| Valid until | Mon, 19 Feb 2035 12:37:02 UTC (expires in 9 years and 6 months) |
| Key | RSA 2048 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | ip-172-26-6-38.ap-southeast-1.compute.internal Self-signed
|
| Signature algorithm | SHA256withRSA |
| Extended Validation | No |
| Certificate Transparency | No |
| OCSP Must Staple | No |
| Revocation information |
None |
| DNS CAA | No (more info) |
| Trusted | No NOT TRUSTED
Mozilla Apple Android Java Windows |
|
Additional Certificates (if supplied)
|
|
| Certificates provided | 1 (875 bytes) |
| Chain issues | None |
|
Certification Paths |
Configuration
| Protocols | |
| TLS 1.3 | Yes |
| TLS 1.2 | Yes* |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
| (*) Experimental: Server negotiated using No-SNI | |
| Cipher Suites | ||
|
# TLS 1.3 (suites in server-preferred order)
|
||
TLS_AES_256_GCM_SHA384 (0x1302)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_CHACHA20_POLY1305_SHA256 (0x1303)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_AES_128_GCM_SHA256 (0x1301)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
128 | |
|
# TLS 1.2 (suites in server-preferred order)
|
||
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
128 | |
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
128 | |
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)
ECDH secp384r1 (eq. 7680 bits RSA) FS
|
256 | |
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e)
DH 4096 bits FS
|
128 | |
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f)
DH 4096 bits FS
|
256 | |
| Handshake Simulation | |||
| Android 4.4.2 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Android 5.0.0 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Android 6.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Android 7.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Android 8.0 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Android 8.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Android 9.0 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| BingPreview Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Chrome 49 / XP SP3 | RSA 2048 (SHA256) | TLS 1.2 > http/1.1 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Chrome 69 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Chrome 70 / Win 10 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Chrome 80 / Win 10 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Firefox 31.3.0 ESR / Win 7 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Firefox 47 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Firefox 49 / XP SP3 | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Firefox 62 / Win 7 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Firefox 73 / Win 10 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Googlebot Feb 2018 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| IE 11 / Win 7 R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| IE 11 / Win 8.1 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| IE 11 / Win Phone 8.1 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| IE 11 / Win Phone 8.1 Update R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| IE 11 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Edge 15 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Edge 16 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Edge 18 / Win 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Edge 13 / Win Phone 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Java 8u161 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Java 11.0.3 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Java 12.0.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| OpenSSL 1.0.1l R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| OpenSSL 1.0.2s R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| OpenSSL 1.1.0k R | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| OpenSSL 1.1.1c R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Safari 6 / iOS 6.0.1 |
Server sent fatal alert: handshake_failure |
||
| Safari 7 / iOS 7.1 R |
Server sent fatal alert: handshake_failure |
||
| Safari 7 / OS X 10.9 R |
Server sent fatal alert: handshake_failure |
||
| Safari 8 / iOS 8.4 R |
Server sent fatal alert: handshake_failure |
||
| Safari 8 / OS X 10.10 R |
Server sent fatal alert: handshake_failure |
||
| Safari 9 / iOS 9 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Safari 9 / OS X 10.11 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Safari 10 / iOS 10 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Safari 10 / OS X 10.12 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Safari 12.1.2 / MacOS 10.14.6 Beta R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Safari 12.1.1 / iOS 12.3.1 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS |
| Apple ATS 9 / iOS 9 R | EC 256 (SHA384) | TLS 1.2 > http/1.1 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| Yahoo Slurp Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 FS |
| YandexBot Jan 2015 | EC 256 (SHA384) | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ECDH secp384r1 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) |
||
| Baidu Jan 2015 |
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 10 / Win Phone 8.0 |
Protocol mismatch (not simulated) |
||
| Java 6u45 No SNI 2 |
Protocol mismatch (not simulated) |
||
| Java 7u25 |
Protocol mismatch (not simulated) |
||
| OpenSSL 0.9.8y |
Protocol mismatch (not simulated) |
||
| Safari 5.1.9 / OS X 10.6.8 |
Protocol mismatch (not simulated) |
||
| Safari 6.0.4 / OS X 10.8.4 R |
Protocol mismatch (not simulated) |
||
| (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 | |
| Secure Renegotiation | Supported |
| Secure Client-Initiated Renegotiation | No |
| Insecure Client-Initiated Renegotiation | No |
| BEAST attack | Mitigated server-side (more info) |
| POODLE (SSLv3) | No, SSL 3 not supported (more info) |
| POODLE (TLS) | No (more info) |
| Zombie POODLE | No (more info) |
| GOLDENDOODLE | No (more info) |
| OpenSSL 0-Length | No (more info) |
| Sleeping POODLE | No (more info) |
| Downgrade attack prevention | Yes, TLS_FALLBACK_SCSV supported (more info) |
| SSL/TLS compression | No |
| RC4 | No |
| Heartbeat (extension) | No |
| Heartbleed (vulnerability) | No (more info) |
| Ticketbleed (vulnerability) | No (more info) |
| OpenSSL CCS vuln. (CVE-2014-0224) | No (more info) |
| OpenSSL Padding Oracle vuln. (CVE-2016-2107) |
No (more info) |
| ROBOT (vulnerability) | No (more info) |
| Forward Secrecy | Yes (with most browsers) ROBUST (more info) |
| ALPN | Yes http/1.1 |
| NPN | No |
| Session resumption (caching) | Yes |
| Session resumption (tickets) | No |
| OCSP stapling | No |
| Strict Transport Security (HSTS) | Yes
max-age=31536000; includeSubdomains; 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) |
| Long handshake intolerance | No |
| TLS extension intolerance | No |
| TLS version intolerance | No |
| Incorrect SNI alerts | No |
| Uses common DH primes | No |
| DH public server param (Ys) reuse | No |
| ECDH public server param reuse | No |
| Supported Named Groups | secp384r1 |
| SSL 2 handshake compatibility | No |
| 0-RTT enabled | No |
|
HTTP Requests
|
|
1 https://xiaode.sg/
(HTTP/1.1 200 OK)
| 1 | |
| Server | nginx | |
| Date | Mon, 28 Jul 2025 04:39:14 GMT | |
| Content-Type | text/html | |
| Content-Length | 515 | |
| Last-Modified | Sun, 23 Feb 2025 15:03:31 GMT | |
| Connection | close | |
| Vary | Accept-Encoding | |
| ETag | "67bb38c3-203" | |
| X-Frame-Options | SAMEORIGIN | |
| Strict-Transport-Security | max-age=31536000; includeSubdomains; preload | |
| X-XSS-Protection | 1; mode=block | |
| Content-Security-Policy | default-src 'self' http://xiaode.sg https://xiaode.sg https://apis.google.com https://accounts.google.com data: blob: 'unsafe-inline' | |
| X-Content-Type-Options | nosniff | |
| X-Served-By | Custom | |
| Referrer-Policy | strict-origin-when-cross-origin | |
| Cache-Control | no-cache | |
| Accept-Ranges | bytes | |
| Miscellaneous | |
| Test date | Mon, 28 Jul 2025 04:39:01 UTC |
| Test duration | 84.676 seconds |
| HTTP status code | 200 |
| HTTP server signature | nginx |
| Server hostname | ec2-3-1-137-222.ap-southeast-1.compute.amazonaws.com |
SSL Report v2.4.1