www.numero.jp
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.
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+ 18.164.52.116 IPv4 WHOIS › A+ 18.164.52.13 IPv4 WHOIS › A+ 18.164.52.69 IPv4 WHOIS › A+ 18.164.52.92 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 | No |
| HSTS | No |
| HSTS Preloading | N/A (HSTS not enabled) |
| 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) |
|---|---|---|
| www.numero.jp | 301 → https://www.numero.jp/ → … → https://numero.jp/ → 200 OK | 301 → https://numero.jp/ → 200 OK |
| numero.jp | 301 → https://numero.jp/ → 200 OK | 200 OK |
- http://www.numero.jp redirects to HTTPS.
DNS Records
As a public resolver answered for www.numero.jp and its domain numero.jp. Looked up 2026-11-09 14:13 UTC · 12 days ago
| Type | Records |
|---|---|
| www.numero.jp | |
| A | |
| AAAA | None |
| MX | 10 inbound-smtp.us-west-2.amazonaws.com |
| SPF | v=spf1 include:amazonses.com ~all |
| numero.jp | |
| A | |
| AAAA | None |
| NS | ns-1480.awsdns-57.org ns-1615.awsdns-09.co.uk ns-245.awsdns-30.com ns-953.awsdns-55.net |
| MX | 10 inbound-smtp.us-west-2.amazonaws.com |
| SPF | v=spf1 include:amazonses.com ~all |
Certificate Identity
| Common Name | www.numero.jp |
| Alt Names | numero.jp www.numero.jp |
| Issuer | CN=Amazon RSA 2048 M04, O=Amazon, C=US |
| Validity | 2026-10-12 to 2027-04-27 (156 days remaining) |
| Key | RSA 2048 bits (sha256RSA) |
| Serial Number | 0287EA828AE3E02CD1C2120F272FAC17 |
| SHA256 Fingerprint | 1da44ed551a698554fae8e9e15602fbb665d1cf31edbd818008f228de1bd60ac |
| Pin SHA256 | V9HcPdb73DyX/NAUpVU/L80SGabIahDO6K3eLDvg2Kc= |
Certificate Properties
| Type | DV Domain Validated |
| Cert Transparency | Yes (SCT) |
| OCSP Must Staple | No |
| Revocation | Good (not revoked) OCSP: http://ocsp.r2m04.amazontrust.com CRL: http://crl.r2m04.amazontrust.com/r2m04.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=numero.jp (Issuer: CN=Amazon RSA 2048 M04, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M04, 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 www.numero.jp, first seen 2026-11-06; current certificate since 2026-11-09.
Certificates served
| Certificate (SHA-256) | Issuer | Valid | Served |
|---|---|---|---|
| 1da44ed551a69855… current | Amazon RSA 2048 M04 | 2026-10-12 → 2027-04-27 | 2026-11-09 |
Addresses
| Address | Certificate | Seen |
|---|---|---|
| 18.164.52.13 | 1da44ed551a69855… | 2026-11-09 |
| 18.164.52.69 | 1da44ed551a69855… | 2026-11-09 |
| 18.164.52.92 | 1da44ed551a69855… | 2026-11-09 |
| 18.164.52.116 | 1da44ed551a69855… | 2026-11-09 |
TLS history (a row per change; repeated checks only extend it)
| Since → last checked (UTC) | Grade | TLS | Certificates | Addresses |
|---|---|---|---|---|
| 2026-11-09 14:13 | A+ | TLS 1.3 | 1da44ed551a69855… | 18.164.52.13, 18.164.52.69, 18.164.52.92, 18.164.52.116 |
Other hosts seen on the same addresses
alquiler.es annunci.repubblica.it cfius.gov dclog.jp fotocasaacademy.es fotocasa.fr hollandandbarrett.be hollandandbarrett.ie jackboxgames.co.uk jackboxgames.de jackboxgames.es jackboxgames.fr jackboxgames.mx ms-fc--match-apigateway-v1.www.fotocasa.es numero.jp onepagecrm.com qa.cloud.whylactate.abbott qa.fsl3.freestyle.abbott qa.libresense.abbott qa.startmyfreestyle.freestyle.abbott s26162.pcdn.co treedis.com www.fotocasaacademy.es www.fotocasa.co.uk www.healthdirect.gov.au www.jackboxgames.co.uk www.jackboxgames.de www.jackboxgames.es www.jackboxgames.fr www.jackboxgames.it