rapidpay.pk
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.
Overall grade based on: IPv4: 4 of 4 complete · IPv6: 4 of 4 complete
All 8 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 13.227.231.123 IPv4 WHOIS › A+ 13.227.231.28 IPv4 WHOIS › A+ 13.227.231.5 IPv4 WHOIS › A+ 13.227.231.62 IPv4 WHOIS › A+ 2600:9000:2035:2800:13:87ff:f240:93a1 IPv6 WHOIS › A+ 2600:9000:2035:2c00:13:87ff:f240:93a1 IPv6 WHOIS › A+ 2600:9000:2035:3800:13:87ff:f240:93a1 IPv6 WHOIS › A+ 2600:9000:2035:4000:13:87ff:f240:93a1 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_128_GCM_SHA256
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768, SecP256r1MLKEM768 |
| HTTP/3 (QUIC) | Yes (advertised) |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Scan Coverage | Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No |
| HSTS | Yes 1 year |
| HSTS Preloading | Not preloadedSubmit → |
| Security Checks | |
| BEAST attack | Mitigated |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | No |
| RC4 | No |
| SSL/TLS Compression | No (not supported by .NET TLS stack) |
| Heartbleed | Not tested |
Cipher Suite Analysis
| Cipher Suite | Hex | Key Exchange | FS | Bits | Strength |
|---|---|---|---|---|---|
| # TLS 1.3 | |||||
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Chrome 80 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Firefox 115 / Win 10 | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| iOS 17 / Safari | TLS 1.3 | TLS_CHACHA20_POLY1305_SHA256 | Success |
| macOS 14 / Safari | TLS 1.3 | TLS_AES_256_GCM_SHA384 | Success |
| Android 14 | TLS 1.3 | TLS_AES_128_GCM_SHA256 | Success |
| Chrome 69 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| 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.
| Host | http:// (port 80) | https:// (port 443) |
|---|---|---|
| rapidpay.pk | 301 → https://rapidpay.pk/ → 200 OK | 200 OK |
| www.rapidpay.pk | 301 → https://www.rapidpay.pk/ → 200 OK | 200 OK |
- http://rapidpay.pk redirects to HTTPS.
DNS Records
As a public resolver answered for rapidpay.pk. Looked up 2026-11-21 05:03 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | 2600:9000:2035:c00:13:87ff:f240:93a1 2600:9000:2035:4600:13:87ff:f240:93a1 2600:9000:2035:ae00:13:87ff:f240:93a1 2600:9000:2035:d600:13:87ff:f240:93a1 2600:9000:2035:e800:13:87ff:f240:93a1 2600:9000:2035:f000:13:87ff:f240:93a1 2600:9000:2035:f400:13:87ff:f240:93a1 2600:9000:2035:fc00:13:87ff:f240:93a1 |
| NS | ns-1092.awsdns-08.org ns-1982.awsdns-55.co.uk ns-324.awsdns-40.com ns-611.awsdns-12.net |
| MX | 10 mx.zoho.com 20 mx2.zoho.com 50 mx3.zoho.com |
| SPF | v=spf1 ip4:207.180.254.56 include:mailbaby.net include:relay.mailbaby.net include:zohomail.com ~all |
Certificate Identity
| Common Name | rapidpay.pk |
| Alt Names | rapidpay.pk checkout.rapidpay.pk www.rapidpay.pk |
| Issuer | CN=Amazon RSA 2048 S18, O=Amazon, C=US |
| Validity | 2026-11-09 to 2027-05-26 (185 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 40F5211F6852E91400F745047376EE21 |
| SHA256 Fingerprint | 672965722ef7b8de5767f501c1f3423f5fe2192702bbe26a91aedad02f9220fd |
| Pin SHA256 | n/D/gMKweWVzbTxH5tRsb95cz1oR3UpoM/yyHDV8nm0= |
Certificate Properties
| Type | DV Domain Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.r2s18.amazontrust.com CRL: http://crl.r2s18.amazontrust.com/Frluo.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 198 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=rapidpay.pk (Issuer: CN=Amazon RSA 2048 S18, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 S18, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
TLS History & Relations
Everything our scans have seen for rapidpay.pk, first seen 2026-11-20; current certificate since 2026-11-21.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 672965722ef7b8de… current | Amazon RSA 2048 S18 | 2026-11-09 → 2027-05-26 | 2026-11-21 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 13.227.231.5 | 672965722ef7b8de… | 2026-11-21 |
| 13.227.231.28 | 672965722ef7b8de… | 2026-11-21 |
| 13.227.231.62 | 672965722ef7b8de… | 2026-11-21 |
| 13.227.231.123 | 672965722ef7b8de… | 2026-11-21 |
| 2600:9000:2035:2800:13:87ff:f240:93a1 | 672965722ef7b8de… | 2026-11-21 |
| 2600:9000:2035:2c00:13:87ff:f240:93a1 | 672965722ef7b8de… | 2026-11-21 |
| 2600:9000:2035:3800:13:87ff:f240:93a1 | 672965722ef7b8de… | 2026-11-21 |
| 2600:9000:2035:4000:13:87ff:f240:93a1 | 672965722ef7b8de… | 2026-11-21 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-21 05:03 | A+ | TLS 1.3 | 672965722ef7b8de… | 13.227.231.5, 13.227.231.28, 13.227.231.62, 13.227.231.123 |
Other hosts seen on the same addresses
aaml.org arizent.arizent.production.k2.m1.brightspot.cloud battlegroundsmobileindia.com cityplumbing.co.uk contributor.huffpost.co.uk dia.com dodoapp.co eap.bl.uk edgenuity.com etext.me exporo.de formulapassion.it futureretail.tech gafasworld.com.co gafasworld.es huffpost.co.uk ibjapan.com icamiami.org intercom-attachments-10.com intercom-attachments-12.com intercom-attachments-8.com kcby.com lentesworld.com.mx oculosworld.com.br oculosworld.com.pt onlyfy.io optykaworld.pl perimeter81.com picmaker.com seopressor.com