shipsltd.co.jp
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 4 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 13.227.173.119 IPv4 WHOIS › A+ 13.227.173.68 IPv4 WHOIS › A+ 13.227.173.70 IPv4 WHOIS › A+ 13.227.173.96 IPv4 WHOIS › 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_128_GCM_SHA256
Protocol Details
| Connection | |
| ALPN | h2 http/1.1 |
| SNI Required | Yes |
| Supported Named Groups | X25519MLKEM768 SecP256r1MLKEM768 x25519 secp256r1 secp384r1 (server preference order) |
| Post-Quantum Key Exchange | Yes X25519MLKEM768, SecP256r1MLKEM768 |
| HTTP/3 (QUIC) | No |
| Encrypted Client Hello | No |
| Security Features | |
| Forward Secrecy | Yes (ECDHE / DHE) |
| Scan Coverage | Incomplete no answer in time for: key exchange groups — shown as unknown, not as unsupported |
| Downgrade Prevention | Yes (legacy TLS disabled) |
| Secure Renegotiation | Supported (RFC 5746) |
| Extended Master Secret | Yes (RFC 7627) |
| OCSP Stapling | Yes |
| 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 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_AES_128_CBC_SHA256 | 0xC027 | ECDHE | FS | 128 | Weak |
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 0xC030 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 | 0xCCA8 | ECDHE | FS | 256 | Secure |
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 0xC028 | ECDHE | FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_GCM_SHA256 | 0x009C | RSA | No FS | 128 | Weak |
| TLS_RSA_WITH_AES_256_GCM_SHA384 | 0x009D | RSA | No FS | 256 | Weak |
| TLS_RSA_WITH_AES_128_CBC_SHA256 | 0x003C | 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_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) |
|---|---|---|
| shipsltd.co.jp | 302 → https://www.shipsltd.co.jp/ → 200 OK | 302 → https://www.shipsltd.co.jp/ → 200 OK |
| www.shipsltd.co.jp | 301 → https://www.shipsltd.co.jp/ → 200 OK | 200 OK |
- http://shipsltd.co.jp redirects to HTTPS.
DNS Records
As a public resolver answered for shipsltd.co.jp. Looked up 2026-11-17 08:19 UTC · today
| Type | Records |
|---|---|
| A | |
| AAAA | None |
| NS | ns-1152.awsdns-16.org ns-1982.awsdns-55.co.uk ns-789.awsdns-34.net ns-86.awsdns-10.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 20 alt2.aspmx.l.google.com 30 aspmx2.googlemail.com 30 aspmx3.googlemail.com 30 aspmx4.googlemail.com 30 aspmx5.googlemail.com |
| SPF | v=spf1 include:_spf.google.com +ip4:202.53.18.99 +ip4:202.53.18.100 +ip4:60.32.134.102 +ip4:163.49.25.24 +ip4:163.49.25.25 +ip4:124.147.16.186 include:spf.ecbeing.co.jp a:cvs.veritrans.co.jp include:amazonses.com ~all |
Certificate Identity
| Common Name | shipsltd.co.jp |
| Alt Names | www.shipsltd.co.jp shipsltd.co.jp |
| Issuer | CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE |
| Validity | 2025-12-09 to 2027-01-10 (53 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 5B711C6F737828274F9B042D |
| SHA256 Fingerprint | 998ceca966f34e691b9a8b3d16ab48db31d637586770cddf7f4222973ba13966 |
| Pin SHA256 | 0nB/zSoJ6W9OFqGxmPBNdOpR7Cci3Fab0jj0jn6Zumg= |
Certificate Properties
| Type | DV |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.globalsign.com/gsgccr3dvtlsca2020 CRL: http://crl.globalsign.com/gsgccr3dvtlsca2020.crl |
| DNS CAA | No (missing) |
| Trusted By | Yes Mozilla · Apple · Android · Java · Windows |
| Name Match | Yes |
| Validity Period | 397 days (maximum 398 days for certificates issued then) |
| Chain Issues | None |
Trust Chain Architecture
End-Entity Certificate
CN=www.shipsltd.co.jp (Issuer: CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE)
Intermediate CA
CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)
Root Certificate
CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3 (Issuer: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3)
TLS History & Relations
Everything our scans have seen for shipsltd.co.jp, first seen 2026-11-17; current certificate since 2026-11-17.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 998ceca966f34e69… current | GlobalSign GCC R3 DV TLS CA 2020 | 2025-12-09 → 2027-01-10 | 2026-11-17 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 13.227.173.68 | 998ceca966f34e69… | 2026-11-17 |
| 13.227.173.70 | 998ceca966f34e69… | 2026-11-17 |
| 13.227.173.96 | 998ceca966f34e69… | 2026-11-17 |
| 13.227.173.119 | 998ceca966f34e69… | 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 08:19 | A+ | TLS 1.3 | 998ceca966f34e69… | 13.227.173.68, 13.227.173.70, 13.227.173.96, 13.227.173.119 |
Other hosts seen on the same addresses
21casino.com acprail.thetrainline-europe.com agriculture.basf.ca app.senato.it asep2014.parlamento.it assets3.novica.net assets.mcnc.org cinema.com.hk classforkids.co.uk coinapp.co consentfox.net consentmanager.dk consentmanager.it contractoruk.com cookiecrawler.net cookiefox.net cookiespider.org deckofcards.net endpoints.news ewebinar.com fantasylife.com getbynder.com helpsns.co.kr hpdsp.jp jacar.go.jp joongna.com kbl.or.kr lab2.lastampa.it lab2.repubblica.it mazzum.co.kr