SSL Check WHOIS
Dashboard / Security Report

payconiq.be

Overall grade based on: IPv4: 4 of 4 complete · IPv6: 0 of 4 complete, 4 pending — IPv6 results are added below when their scan finishes; they do not count until then.
IPv6 scan in progress
2600:9000:2035:1000:12:e164:bec0:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2035:1600:12:e164:bec0:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2035:1a00:12:e164:bec0:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2600:9000:2035:3c00:12:e164:bec0:93a1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).

The IPv4 report below is complete. IPv6 results will be added to this page automatically when the scan finishes.

All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 13.227.231.115 IPv4 WHOIS › A+ 13.227.231.121 IPv4 WHOIS › A+ 13.227.231.128 IPv4 WHOIS › A+ 13.227.231.67 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-06 03:34 UTC

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) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (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 No
HSTS Preloading N/A (HSTS not enabled)
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_128_GCM_SHA2560x1301ECDHEFS128Secure
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
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_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
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)
payconiq.be301 → https://payconiq.be/ → … → https://www.bancontact.com/nl → 200 OK302 → https://www.payconiq.be/ → … → https://www.bancontact.com/nl → 200 OK
www.payconiq.be301 → https://www.payconiq.be/ → … → https://www.bancontact.com/nl → 200 OK302 → https://www.bancontact.com/ → … → https://www.bancontact.com/nl → 200 OK
  • http://payconiq.be redirects to HTTPS.

DNS Records

As a public resolver answered for payconiq.be. Looked up 2026-11-06 03:34 UTC · 11 days ago

TypeRecords
A
AAAA
NS
ns-1340.awsdns-39.org ns-1797.awsdns-32.co.uk ns-288.awsdns-36.com ns-722.awsdns-26.net
MX
0 payconiq-be.mail.protection.outlook.com
SPF
v=spf1 include:spf.flexmail.eu include:_spf.atlassian.net include:spf.protection.outlook.com include:sendgrid.net include:_spf.salesforce.com ip4:185.111.196.239 ip4:81.4.74.113 -all

Certificate Identity

Common Namepayconiq.be
Alt Names bancontact.com contact.payconiq.be www.payconiq.be www.bancontact.com www.bancontactpayconiq.com payconiq.be bancontactpayconiq.com
IssuerCN=Amazon RSA 2048 M01, O=Amazon, C=US
Validity 2026-08-16 to 2027-03-01 (104 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number0741097909915DAF1EB4F5675FC8DC0D
SHA256 Fingerprint b45581ec0dc770e9c07927192c821388d3f06c2ac4d98b213dfd4cc2ee3095d8
Pin SHA256SbCeA5sFvAQiQHIXbyT+kkPQeLkWuCzyOxjxEYoa0lA=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m01.amazontrust.com CRL: http://crl.r2m01.amazontrust.com/r2m01.crl
DNS CAA Yes (configured) 0 iodef "mailto:[email protected]" 0 issue "amazon.com" 0 issue "globalsign.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=bancontact.com (Issuer: CN=Amazon RSA 2048 M01, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M01, 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 payconiq.be, first seen 2026-10-29; current certificate since 2026-11-06.

Certificates served

Certificate (SHA-256)IssuerValidServed
b45581ec0dc770e9… current Amazon RSA 2048 M012026-08-16 → 2027-03-012026-11-06

Addresses

AddressCertificateSeen
13.227.231.67 b45581ec0dc770e9… 2026-11-06
13.227.231.115 b45581ec0dc770e9… 2026-11-06
13.227.231.121 b45581ec0dc770e9… 2026-11-06
13.227.231.128 b45581ec0dc770e9… 2026-11-06

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-06 03:34A+TLS 1.3 b45581ec0dc770e9… 13.227.231.67, 13.227.231.115, 13.227.231.121, 13.227.231.128

Other domains on the same certificate

Other hosts seen on the same addresses