SSL Check WHOIS
Dashboard / Security Report

telesystem.us

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+ 199.60.103.226 IPv4 WHOIS › A+ 199.60.103.30 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-07 10:32 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 No (certificate has no OCSP responder)
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_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA2560xCCA9ECDHEFS256Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure

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_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_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)
telesystem.us301 → https://www.trusttelesystem.com/ → 200 OK301 → https://www.trusttelesystem.com/ → 200 OK
www.telesystem.us301 → https://www.trusttelesystem.com/ → 200 OK301 → https://www.trusttelesystem.com/ → 200 OK
  • http://telesystem.us redirects to HTTPS.
  • https://telesystem.us forwards visitors to www.trusttelesystem.com, a different site. View its report ›

DNS Records

As a public resolver answered for telesystem.us. Looked up 2026-11-07 10:32 UTC · today

TypeRecords
A
AAAA None
NS
ns1.buckeyecom.net ns2.buckeyecom.net ns3.buckeyecom.net
MX
10 telesystem-us.mail.protection.outlook.com
SPF
v=spf1 mx ip4:72.240.36.32/27 ip4:72.240.1.246 ip4:192.254.121.248 ip4:208.84.248.11 ip4:52.203.41.93 ip4:208.84.251.130 include:_spf.coredial.com include:spf.protection.outlook.com include:spf.us.exclaimer.net -all

Certificate Identity

Common Nametelesystem.us
Alt Names 4f741a3a.sni.cloudflaressl.com telesystem.us
IssuerCN=WE1, O=Google Trust Services, C=US
Validity 2026-10-18 to 2027-01-16 (69 days remaining)
KeyECDSA 256 bits (sha256ECDSA)
Serial Number00F46E4677FDB0ADF21398AB37BB7E2FB5
SHA256 Fingerprint b0e1b397567ebe7d9fb6b65f199838ef0212f4403e5429ead17386eb8880154a
Pin SHA256oaA7Z/KXFvwVbvMVDPoM6X0eTIeNV/2Q3yk6wyI/HNo=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) CRL: http://c.pki.goog/we1/f_bY-wXbefM.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=4f741a3a.sni.cloudflaressl.com (Issuer: CN=WE1, O=Google Trust Services, C=US)
Intermediate CA
CN=WE1, O=Google Trust Services, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)
Root Certificate
CN=GTS Root R4, O=Google Trust Services LLC, C=US (Issuer: CN=GTS Root R4, O=Google Trust Services LLC, C=US)

TLS History & Relations

Everything our scans have seen for telesystem.us, first seen 2026-11-07; current certificate since 2026-11-07.

Certificates served

Certificate (SHA-256)IssuerValidServed
b0e1b397567ebe7d… current WE12026-10-18 → 2027-01-162026-11-07

Addresses

AddressCertificateSeen
199.60.103.30 b0e1b397567ebe7d… 2026-11-07
199.60.103.226 b0e1b397567ebe7d… 2026-11-07

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-07 10:32A+TLS 1.3 b0e1b397567ebe7d… 199.60.103.30, 199.60.103.226

Other domains on the same certificate

Other hosts seen on the same addresses