gendo.app
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
B 3.95.124.252 IPv4 WHOIS › B 34.225.7.26 IPv4 WHOIS › Grade Breakdown
Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.
Security Vulnerabilities Detected
- •Obsolete TLS versions (1.0/1.1) supported.
- •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).
Protocol Configuration
Supported Protocols
TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2
Negotiated Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | No |
| Supported Named Groups | secp256r1 (inferred) |
| Post-Quantum Key Exchange | No (no hybrid ML-KEM group such as X25519MLKEM768) |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Unknown |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | No |
| HSTS | No |
| HSTS Preloading | Preloaded |
| Security Checks | |
| BEAST attack | Not mitigated server-side (TLS 1.0 + CBC) |
| POODLE (SSLv3) | No (SSL 3 not supported) |
| POODLE (TLS) | Possible (CBC + legacy TLS present) |
| 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.2 | |||||
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 0xC02F | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
Handshake Simulation
| Client | Protocol | Cipher Suite | Result |
|---|---|---|---|
| Chrome 120 / Win 11 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Chrome 80 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Firefox 115 / Win 10 | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| iOS 17 / Safari | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| macOS 14 / Safari | TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | Success |
| Android 14 | TLS 1.2 | TLS_ECDHE_RSA_WITH_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 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | Success |
* 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) |
|---|---|---|
| gendo.app | 302 → https://www.gendo.app/ → … → https://www.gendo.app/br → 200 OK | 302 → https://www.gendo.app/ → … → https://www.gendo.app/br → 200 OK |
| www.gendo.app | 308 → https://www.gendo.app/ → … → https://www.gendo.app/br → 200 OK | 307 → https://www.gendo.app/br → 200 OK |
- http://gendo.app redirects to HTTPS.
DNS Records
As a public resolver answered for gendo.app. Looked up 2026-11-17 23:59 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns-1364.awsdns-42.org ns-1703.awsdns-20.co.uk ns-378.awsdns-47.com ns-516.awsdns-00.net |
| 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.google.com ~all |
Certificate Identity
| Common Name | gendo.app |
| Alt Names | *.gendo.com.br *.gendo.app *.superagendador.com *.app.gendo.com.br gendo.app *.adm.gendo.app *.app.superagendador.com gendo.com.br *.adm.gendo.com.br superagendador.com *.gestor.superagendador.com |
| Issuer | CN=Amazon RSA 2048 S21, O=Amazon, C=US |
| Validity | 2026-11-15 to 2027-06-01 (195 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 41E9266B8163AC37C1C2C6577A48099B |
| SHA256 Fingerprint | 04f2f1ea5b2e13c028fcf54ab90e759319f288b622cdc4a32f04c62dc84ab375 |
| Pin SHA256 | vTNXp2LNvJ5gUTc1iIfYeWWD5G8f4d65EL225emFe48= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.r2s21.amazontrust.com CRL: http://crl.r2s21.amazontrust.com/2W8sm.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 198 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=*.gendo.com.br (Issuer: CN=Amazon RSA 2048 S21, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 S21, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
TLS History & Relations
Everything our scans have seen for gendo.app, first seen 2026-11-17; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 04f2f1ea5b2e13c0… current | Amazon RSA 2048 S21 | 2026-11-15 → 2027-06-01 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 3.95.124.252 | 04f2f1ea5b2e13c0… | 2026-11-17 |
| 34.225.7.26 | 04f2f1ea5b2e13c0… | 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 23:59 | B | TLS 1.2 | 04f2f1ea5b2e13c0… | 3.95.124.252, 34.225.7.26 |
Other domains on the same certificate
- gendo.com.br 4 names *.adm.gendo.com.br *.app.gendo.com.br *.gendo.com.br
- superagendador.com 4 names *.app.superagendador.com *.gestor.superagendador.com *.superagendador.com