www.pay.nl
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 › 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 Secrecy | Yes (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 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_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | 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) |
|---|---|---|
| www.pay.nl | 301 → https://www.pay.nl/ → 200 OK | 200 OK |
| pay.nl | 301 → https://www.pay.nl/ → 200 OK | 301 → https://www.pay.nl/ → 200 OK |
- http://www.pay.nl redirects to HTTPS.
DNS Records
As a public resolver answered for www.pay.nl and its domain pay.nl. Looked up 2026-11-17 20:49 UTC · today
| Type | Records |
|---|---|
| www.pay.nl | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| pay.nl | |
| A | |
| AAAA | None |
| NS | anycast-eu.dns.cyso.eu anycast-global.dns.cyso.net unicast-eu.dns.cyso.nl |
| MX | 10 pay-nl.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 Name | www.pay.nl |
| Alt Names | pay.nl www.pay.nl pay.be www.pay.be |
| Issuer | CN=PerfectSSL, O=PerfectSSL, C=NL |
| Validity | 2026-01-28 to 2027-02-26 (101 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 01513128D7C25916C7D53D79421BF550 |
| SHA256 Fingerprint | 783e28004e4cf53fa0e1317cf08859be3120d3246b213f1e7a9e75aefe8e83f6 |
| Pin SHA256 | BaMS+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; cansignhttpexchanges=yes" 0 issue "geotrust.com" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issue "sectigo.com" 0 issue "visa.com" |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 395 days (maximum 398 days for certificates issued then) |
| Chain Issues | None |
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.nl, first seen 2026-10-28; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 783e28004e4cf53f… current | PerfectSSL | 2026-01-28 → 2027-02-26 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 141.101.90.96 | 783e28004e4cf53f… | 2026-11-17 |
| 141.101.90.97 | 783e28004e4cf53f… | 2026-11-17 |
| 141.101.90.98 | 783e28004e4cf53f… | 2026-11-17 |
| 141.101.90.99 | 783e28004e4cf53f… | 2026-11-17 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-17 20:49 | A+ | 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
- pay.be 2 names
Other hosts seen on the same addresses
bertrand.pt blogthinkbig.com bretagne.bzh cepi.net ciphr.com curved.de emcdda.europa.eu e-tar.lt iledefrance-mobilites.fr infopedia.pt jyskebank.dk kam.lt lrp.lt lrs.lt lrv.lt mediamarkt.ch mediamarkt.com.tr mediamarkt.pl ncoi.nl schuelerhilfe.de stat.gov.lt sygnum.com telefonica.com telefonica.es vmi.lt www.1und1.de www.pay.be