SSL Check WHOIS
upsc.gov.in has no HTTPS: HTTPS could not be reached on its IPv4 address. The site is served on www.upsc.gov.in; this is its report. (upsc.gov.in checked 2026-07-27 13:57 UTC)
Dashboard / Security Report

www.upsc.gov.in

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

www.upsc.gov.in: SSL/TLS grade A+ (HTTPS Monitor)www.upsc.gov.inA+
Overall grade based on: IPv4: 2 of 2 complete · IPv6: 2 of 2 complete
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 104.117.77.40 IPv4 WHOIS › A+ 104.117.77.91 IPv4 WHOIS › A+ 2a02:26f0:3900::6875:4d6b IPv6 WHOIS › A+ 2a02:26f0:3900::6875:4d98 IPv6 WHOIS ›

Grade Breakdown

Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 x25519 secp256r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768
HTTP/3 (QUIC) Yes (advertised)
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret No
OCSP Stapling No (certificate has no OCSP responder)
HSTS Yes 182 days
HSTS Preloading Not preloadedSubmit →
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Success
Android 4.0.4--No
Android 4.1.1--No
Baidu Jan 2015--No
Java 6--No

* Simulated based on server's supported protocols and cipher configuration.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
www.upsc.gov.in403 Forbidden (unencrypted)403 Forbidden
upsc.gov.inNo answer (timed out)No answer (timed out)
  • http://www.upsc.gov.in answers without redirecting to HTTPS: visitors who type the address without https:// get an unencrypted page.
  • upsc.gov.in has no working HTTPS (no answer): visitors who type that name do not reach the HTTPS site.

DNS Records

As a public resolver answered for www.upsc.gov.in and its domain upsc.gov.in. Looked up 2026-11-18 17:11 UTC · 4 days ago

TypeRecords
www.upsc.gov.in
A
AAAA
MX None
SPF None
upsc.gov.in
A
AAAA None
NS
ns1.nic.in ns10.nic.in ns11.nic.in ns2.nic.in ns7.nic.in
MX
10 mx.mgovcloud.in
SPF None

Certificate Identity

Common Namewww.upsc.gov.in
Alt Names www.upsc.gov.in
IssuerCN=YR2, O=Let's Encrypt, C=US
Validity 2026-10-13 to 2027-01-11 (49 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0631A7C839D56D922DD297DBDA789BC3B1D1
SHA256 Fingerprint c97dad9748c3f3f19c60d42371fdec251ee2e93ef5e7c238accb3645e38a0083
Pin SHA256KAHrhJUfa+tdz3JpC6x5VSEi1Khnsp3YsgKAprjQ8Ug=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr2.c.lencr.org/82.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA Yes (configured) 0 issue "letsencrypt.org" 0 issuewild "letsencrypt.org"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 90 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=www.upsc.gov.in (Issuer: CN=YR2, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR2, O=Let's Encrypt, C=US (Issuer: CN=Root YR, O=ISRG, C=US)
Intermediate CA
CN=Root YR, O=ISRG, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)
Root Certificate
CN=ISRG Root X1, O=Internet Security Research Group, C=US (Issuer: CN=ISRG Root X1, O=Internet Security Research Group, C=US)

Certificates & Relations

The current state of www.upsc.gov.in as of our latest scan; certificate changed 2026-11-18.

Certificates served

Certificate (SHA-256)IssuerValid
c97dad9748c3f3f1…YR22026-10-13 → 2027-01-11

Addresses

AddressAS
104.117.77.40 —
104.117.77.91 —

Other hosts on the same addresses