SSL Check WHOIS
Dashboard / Security Report

www.pay.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
2a06:98c1:3200::90:0 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a06:98c1:3200::90:1 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a06:98c1:3200::90:2 IPv6 · Pending: IPv6 scan not started yet (it runs when the report is opened, or via POST /api/ssl-check/{domain}/ipv6).
2a06:98c1:3200::90:3 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+ 141.101.90.96 IPv4 WHOIS › A+ 141.101.90.97 IPv4 WHOIS › A+ 141.101.90.98 IPv4 WHOIS › A+ 141.101.90.99 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-11 20:43 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_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
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 Yes (RFC 7627)
OCSP Stapling Yes
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 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_CHACHA20_POLY1305_SHA2560xCCA8ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure

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)
www.pay.be301 → https://www.pay.nl/ → 200 OK301 → https://www.pay.nl/ → 200 OK
pay.be301 → https://www.pay.nl/ → 200 OK301 → https://www.pay.nl/ → 200 OK
  • http://www.pay.be redirects to HTTPS.
  • https://www.pay.be forwards visitors to www.pay.nl, a different site. View its report ›

DNS Records

As a public resolver answered for www.pay.be and its domain pay.be. Looked up 2026-11-11 20:43 UTC · 5 days ago

TypeRecords
www.pay.be
A
AAAA
MX None
SPF None
pay.be
A
AAAA None
NS
anycast-eu.dns.cyso.eu anycast-global.dns.cyso.net unicast-eu.dns.cyso.nl
MX
10 pay-be.mail.protection.outlook.com
SPF
v=spf1 mx a ip4:85.158.206.16/29 ip4:37.46.136.0/24 ip4:37.46.137.128/27 include:fdspfeuc.freshemail.io include:spf.otys.nl include:sendgrid.net include:25758250.spf03.hubspotemail.net include:spf.protection.outlook.com -all

Certificate Identity

Common Namewww.pay.be
Alt Names pay.nl www.pay.nl pay.be www.pay.be
IssuerCN=PerfectSSL, O=PerfectSSL, C=NL
Validity 2026-01-28 to 2027-02-26 (101 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number01513128D7C25916C7D53D79421BF550
SHA256 Fingerprint 783e28004e4cf53fa0e1317cf08859be3120d3246b213f1e7a9e75aefe8e83f6
Pin SHA256BaMS+Wq4e2kUf49xr1f5KW1eTxsy5aQlLdk8qHk5gvU=

Certificate Properties

Type EV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/PerfectSSL.crl
DNS CAA Yes (configured) 0 iodef "mailto:[email protected]" 0 issue "digicert.com" 0 issue "sectigo.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 395 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=pay.nl, O=Tintel B.V., L=Enschede, S=Overijssel, C=NL, SERIALNUMBER=24283498, businessCategory=Private Organization, jurisdictionCountryName=NL (Issuer: CN=PerfectSSL, O=PerfectSSL, C=NL)
Intermediate CA
CN=PerfectSSL, O=PerfectSSL, C=NL (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

Everything our scans have seen for www.pay.be, first seen 2026-10-28; current certificate since 2026-11-11.

Certificates served

Certificate (SHA-256)IssuerValidServed
783e28004e4cf53f… current PerfectSSL2026-01-28 → 2027-02-262026-11-11

Addresses

AddressCertificateSeen
141.101.90.96 783e28004e4cf53f… 2026-11-11
141.101.90.97 783e28004e4cf53f… 2026-11-11
141.101.90.98 783e28004e4cf53f… 2026-11-11
141.101.90.99 783e28004e4cf53f… 2026-11-11

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-11 20:43A+TLS 1.3 783e28004e4cf53f… 141.101.90.96, 141.101.90.97, 141.101.90.98, 141.101.90.99

Other domains on the same certificate

Other hosts seen on the same addresses