SSL Check WHOIS
Dashboard / Security Report

biddz.io

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.

biddz.io: SSL/TLS grade A+ (HTTPS Monitor)biddz.ioA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 75.2.70.75 IPv4 WHOIS › A+ 99.83.190.102 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-22 07:05 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 http/1.1
SNI Required Yes
Supported Named Groups secp256r1 secp384r1 (server preference order)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
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 No (certificate has no OCSP responder)
HSTS Unknown (the HTTPS request to this IP failed)
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_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure
# 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
TLS_DHE_RSA_WITH_AES_128_GCM_SHA2560x009EDHEFS128Secure
TLS_DHE_RSA_WITH_AES_256_GCM_SHA3840x009FDHEFS256Secure

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)
biddz.io301 → https://biddz.io/ → … → https://www.biddz.io/ → 200 OK301 → https://www.biddz.io/ → 200 OK
www.biddz.io301 → https://www.biddz.io/ → 200 OK200 OK
  • http://biddz.io redirects to HTTPS.

DNS Records

As a public resolver answered for biddz.io. Looked up 2026-11-22 07:05 UTC · today

TypeRecords
A
AAAA None
NS
pdns03.domaincontrol.com pdns04.domaincontrol.com
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
SPF
v=spf1 include:spf.sendinblue.com mx ~all v=spf1 include:_spf.google.com include:spf.mandrillapp.com ~all v=spf1 include:_spf.google.com ~all
More than one SPF policy: receivers treat this as an error and SPF fails (RFC 7208).

Certificate Identity

Common Namebiddz.io
Alt Names biddz.io
IssuerCN=YR1, O=Let's Encrypt, C=US
Validity 2026-10-28 to 2027-01-26 (64 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number069CC18CA358AB46E15F09A4EB5D7950F8DB
SHA256 Fingerprint d938a0afff8e01fbfb7df2e708802c1f7c2de482ce0a0e3f8bad619a69bd7108
Pin SHA256btXsRd7cj7HlKd0afM3DgrUQjg1HMO/wATam8r+cjJQ=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://yr1.c.lencr.org/92.crl No OCSP responder — revocation is published via CRL only (as CA/B Forum rules now allow).
DNS CAA No (missing)
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=biddz.io (Issuer: CN=YR1, O=Let's Encrypt, C=US)
Intermediate CA
CN=YR1, 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)

TLS History & Relations

Everything our scans have seen for biddz.io, first seen 2026-11-22; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
d938a0afff8e01fb… current YR12026-10-28 → 2027-01-262026-11-22

Addresses

AddressCertificateSeen
75.2.70.75 d938a0afff8e01fb… 2026-11-22
99.83.190.102 d938a0afff8e01fb… 2026-11-22

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 07:05A+TLS 1.3 d938a0afff8e01fb… 75.2.70.75, 99.83.190.102

Other hosts seen on the same addresses