tmf-group.com has no HTTPS: HTTPS could not be reached on all 2 IPv4 addresses. The site is served on www.tmf-group.com; this is its report. (tmf-group.com checked 2026-08-15 17:15 UTC)
www.tmf-group.com
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: 2 of 2 complete · IPv6: 2 of 2 complete
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 104.18.37.162 IPv4 WHOIS › A+ 172.64.150.94 IPv4 WHOIS › A+ 2606:4700:4403::ac40:965e IPv6 WHOIS › A+ 2606:4700:440b::6812:25a2 IPv6 WHOIS › Grade Breakdown
Protocol Support 95%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Certificate expires in 13 days. This domain's SSL/TLS certificate needs to be renewed soon to avoid service disruption.
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 · includeSubDomains |
| 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.tmf-group.com | 301 → https://www.tmf-group.com/ → 200 OK | 200 OK |
| tmf-group.com | 301 → https://www.tmf-group.com/ → 200 OK | TLS handshake failed |
- http://www.tmf-group.com redirects to HTTPS.
- tmf-group.com has no working HTTPS (TLS handshake failed): visitors who type that name do not reach the HTTPS site.
DNS Records
As a public resolver answered for www.tmf-group.com and its domain tmf-group.com. Looked up 2026-11-18 20:02 UTC · 2 days ago
| Type | Records |
|---|---|
| www.tmf-group.com | |
| A | |
| AAAA | |
| MX | None |
| SPF | None |
| tmf-group.com | |
| A | |
| AAAA | |
| NS | ns01.brandshelter.com ns02.brandshelter.net |
| MX | 0 eu-smtp-inbound-1.mimecast.com 0 eu-smtp-inbound-2.mimecast.com |
| SPF | v=spf1 exists:%{l}.t1.%{i}.t2.%{d}.t3.4qNUuNkfgW.t4.spf.tdmarc.threatcop.com include:spf-b.tmf-group.com include:spf-partners.tmf-group.com include:spf.protection.outlook.com include:eu._netblocks.mimecast.com include:0b443edc-spf.mta.getcheckrecipient.com include:spfhost.messageprovider.com include:spf.sendinblue.com ~all |
Certificate Identity
| Common Name | www.tmf-group.com |
| Alt Names | tmf-group.com prod.tmf-group.com qa.tmf-group.com uat.tmf-group.com www.tmf-group.com |
| Issuer | CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB |
| Validity | 2025-12-04 to 2026-12-04 (13 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 008D62299F93D0A548C82ED5CA07CAF9D4 |
| SHA256 Fingerprint | cca01e18b81d7fb6b66e9239f506c6d63667ab94846af9533e3b1d209df7f011 |
| Pin SHA256 | DOEH4nJzEMakJ7a+TssiOQoklgazNwHmkeF3W509hqE= |
Certificate Properties
| Type | OV Organization Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.sectigo.com CRL: http://crl.sectigo.com/SectigoPublicServerAuthenticationCAOVR36.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 366 days (maximum 398 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=tmf-group.com, O=TMF Group B.V., S=Noord-Holland, C=NL (Issuer: CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB)
Intermediate CA
CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
Root Certificate
CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB (Issuer: CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB)
TLS History & Relations
Everything our scans have seen for www.tmf-group.com, first seen 2026-11-18; current certificate since 2026-11-18.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| cca01e18b81d7fb6… current | Sectigo Public Server Authentication CA OV R36 | 2025-12-04 → 2026-12-04 | 2026-11-18 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 104.18.37.162 | cca01e18b81d7fb6… | 2026-11-18 |
| 172.64.150.94 | cca01e18b81d7fb6… | 2026-11-18 |
| 2606:4700:4403::ac40:965e | cca01e18b81d7fb6… | 2026-11-18 |
| 2606:4700:440b::6812:25a2 | cca01e18b81d7fb6… | 2026-11-18 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-18 20:02 | A+ | TLS 1.3 | cca01e18b81d7fb6… | 104.18.37.162, 172.64.150.94 |