hr.type.jp
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 2.22.250.156 IPv4 WHOIS › B 2.22.250.175 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_AES_256_GCM_SHA384
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 x25519 secp256r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Downgrade Prevention | Yes (TLS_FALLBACK_SCSV) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | Yes |
| HSTS | No |
| HSTS Preloading | N/A (HSTS not enabled) |
| 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.3 | |||||
| TLS_AES_256_GCM_SHA384 | 0x1302 | ECDHE | FS | 256 | Secure |
| TLS_CHACHA20_POLY1305_SHA256 | 0x1303 | ECDHE | FS | 256 | Secure |
| TLS_AES_128_GCM_SHA256 | 0x1301 | ECDHE | FS | 128 | Secure |
| TLS_AES_128_CCM_SHA256 | 0x1304 | ECDHE | FS | 128 | Secure |
| # TLS 1.2 | |||||
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 0xC02C | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 0xC02B | ECDHE | FS | 128 | Secure |
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA9 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| 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_ECDSA_WITH_AES_256_CBC_SHA384 | 0xC024 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | 0xC023 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | 0xC014 | ECDHE | FS | 256 | Weak |
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | 0xC013 | ECDHE | FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA256 | 0x003D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_CBC_SHA | 0x0035 | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA | 0x002F | RSA | No FS | 128 | Weak |
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_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Chrome 49 / XP SP3 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 10 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| IE 11 / Win 7 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 9.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 7.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 5.0 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.4.2 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 11 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Java 8u121 | TLS 1.2 | TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | Success |
| Android 4.0.4 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Android 4.1.1 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Baidu Jan 2015 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | Success |
| Java 6 | TLS 1.0 | TLS_ECDHE_RSA_WITH_AES_256_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) |
|---|---|---|
| hr.type.jp | 301 → https://hr.type.jp/ → 200 OK | 200 OK |
- http://hr.type.jp redirects to HTTPS.
Certificate Identity
| Common Name | hr.type.jp |
| Alt Names | type.jp adm.type.jp bko.type.jp hr.type.jp |
| Issuer | CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US |
| Validity | 2026-08-07 to 2027-02-21 (95 days remaining) |
| Key | ECDSA 256 bits (sha384ECDSA) |
| Serial Number | 0CEB2C568D38F0BF4CC89D6D87874B2A |
| SHA256 Fingerprint | 5e737e3030a84bb91c3b96b7f142a1dc1f093ab709499c7ef5b8ce40225f715f |
| Pin SHA256 | UXYQI+3Br7y0emm1159kZF1fqt/EKeRa3MwISvb3bMs= |
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/DigiCertGlobalG3TLSECCSHA3842020CA1-2.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 199 days (maximum 200 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=type.jp, O="CAREER DESIGN CENTER CO.,LTD.", L=Minato-Ku, S=Tokyo, C=JP, SERIALNUMBER=0104-01-008039, businessCategory=Private Organization, jurisdictionCountryName=JP (Issuer: CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
TLS History & Relations
Everything our scans have seen for hr.type.jp, first seen 2026-08-03; current certificate since 2026-11-02.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 5e737e3030a84bb9… current | DigiCert Global G3 TLS ECC SHA384 2020 CA1 | 2026-08-07 → 2027-02-21 | 2026-11-02 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 2.22.250.156 | 5e737e3030a84bb9… | 2026-11-02 |
| 2.22.250.175 | 5e737e3030a84bb9… | 2026-11-02 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-02 08:58 | B | TLS 1.3 | 5e737e3030a84bb9… | 2.22.250.156, 2.22.250.175 |