ascii.jp is registered with whois.jprs.jp and is hosted on AS16509 Amazon.com Inc. in India. Its SSL certificate from Amazon expired on 19 Apr 2025. WOT's community rates its safety excellent (90/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is ascii.jp’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Japan | 97.9% | 8,535,655 | 4.4% | 95.6% |
| United States | 1.5% | 134,656 | 23.6% | 76.4% |
| Canada | 17% | 14,967 | 2.7% | 97.3% |
| Singapore | 8% | 6,651 | 14.2% | 85.8% |
| Argentina | 8% | 7,246 | 0% | 100% |
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address ascii.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| ascii.jp | 18.164.217.23 | 60 |
| ascii.jp | 18.164.217.26 | 60 |
| ascii.jp | 18.164.217.61 | 60 |
| ascii.jp | 18.164.217.8 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| ascii.jp | 1 aspmx.l.google.com | 60 |
| ascii.jp | 5 alt1.aspmx.l.google.com | 60 |
| ascii.jp | 5 alt2.aspmx.l.google.com | 60 |
| ascii.jp | 10 alt3.aspmx.l.google.com | 60 |
| ascii.jp | 10 alt4.aspmx.l.google.com | 60 |
| Host | Name server | TTL |
|---|---|---|
| ascii.jp | ns-1186.awsdns-20.org | 300 |
| ascii.jp | ns-1549.awsdns-01.co.uk | 300 |
| ascii.jp | ns-467.awsdns-58.com | 300 |
| ascii.jp | ns-959.awsdns-55.net | 300 |
| Host | Text | TTL |
|---|---|---|
| ascii.jp | "202310201811066E6C2F44F4E9521B0891839BBA246CC4035E967F31D248481CF2BAEF24ACF1F7" | 600 |
| ascii.jp | "google-site-verification=4RFrTJvPHs8vN5NYsS5jaXkKSbUxo35wzYiF2KYAPNM" | 600 |
| ascii.jp | "google-site-verification=l00hoOWVjQHk9Wj7-5Hxg8-SPzutL4qKV7h5mTRXqTY" | 600 |
| ascii.jp | "v=spf1 +mx +ip4:3.114.199.146 ~all" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| ascii.jp | ns-1549.awsdns-01.co.uk awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 18.164.217.23. Normal for shared hosting and CDNs.
No reviews yet. Used ascii.jp? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates ascii.jp excellent for safety (90/100). Its SSL certificate expired on 19 Apr 2025. See Security →
ascii.jp is registered through whois.jprs.jp. See WHOIS →
ascii.jp is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in India. See Hosting →
We detected 3 technologies, including Google Analytics, jQuery and Bootstrap CDN. See Built with →
Raw registry data for ascii.jp. May be redacted by privacy services.
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: [ドメイン情報] [Domain Name] ASCII.JP [登録者名] 株式会社KADOKAWA [Registrant] KADOKAWA CORPORATION [Name Server] ns-1186.awsdns-20.org [Name Server] ns-1549.awsdns-01.co.uk [Name Server] ns-959.awsdns-55.net [Name Server] ns-467.awsdns-58.com [Signing Key] [登録年月日] 2016/03/03 [有効期限] 2025/03/31 [状態] Active [最終更新] 2024/04/01 01:05:04 (JST) Contact Information: [公開連絡窓口] [名前] 株式会社KADOKAWA [Name] KADOKAWA CORPORATION [Email] [email protected] [Web Page] [郵便番号] 102-8177 [住所] 東京都千代田区 富士見 2-13-3 [Postal Address] Chiyoda City 2-13-3 Fujimi [電話番号] 0366759363 [FAX番号]
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with ascii.jp. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.