sankei.jp was registered with whois.jprs.jp on 5 Aug 1986 and is hosted on AS16509 Amazon.com Inc. in India. Its SSL certificate from Amazon expired on 12 Jun 2024, and the site does not support HTTP/3. WOT's community rates its safety good (72/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 sankei.jp’s name taken on other extensions?
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address sankei.jp resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| sankei.jp | 18.66.63.2 | 26 |
| sankei.jp | 18.66.63.41 | 26 |
| sankei.jp | 18.66.63.7 | 26 |
| sankei.jp | 18.66.63.8 | 26 |
| Host | Name server | TTL |
|---|---|---|
| sankei.jp | ns-110.awsdns-13.com | 21600 |
| sankei.jp | ns-1242.awsdns-27.org | 21600 |
| sankei.jp | ns-1923.awsdns-48.co.uk | 21600 |
| sankei.jp | ns-648.awsdns-17.net | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| sankei.jp | ns-648.awsdns-17.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 18.66.63.7. Normal for shared hosting and CDNs.
No reviews yet. Used sankei.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 sankei.jp good for safety (72/100). Its SSL certificate expired on 12 Jun 2024. See Security →
sankei.jp is registered through whois.jprs.jp. See WHOIS →
sankei.jp was registered on 5 Aug 1986, making it 40 years old. See Overview →
sankei.jp is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in India. See Hosting →
We detected 3 technologies, including Google Analytics, WordPress and jQuery. See Built with →
Raw registry data for sankei.jp. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: JP organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan contact: administrative name: Koki Higashida organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan phone: +81 3 5215 8451 fax-no: +81 3 5215 8452 e-mail: [email protected] contact: technical name: Koki Higashida organisation: Japan Registry Services Co., Ltd. address: Chiyoda First Bldg. East 13F address: 3-8-1 Nishi-Kanda address: Chiyoda-ku Tokyo 101-0065 address: Japan phone: +81 3 5215 8480 fax-no: +81 3 5215 8452 e-mail: [email protected] nserver: A.DNS.JP 2001:dc4:0:0:0:0:0:1 203.119.1.1 nserver: B.DNS.JP 2001:dc2:0:0:0:0:0:1 202.12.30.131 nserver: C.DNS.JP 156.154.100.5 2001:502:ad09:0:0:0:0:5 nserver: D.DNS.JP 2001:240:0:0:0:0:0:53 210.138.175.244 nserver: E.DNS.JP 192.50.43.53 2001:200:c000:0:0:0:0:35 nserver: F.DNS.JP 150.100.6.8 2001:2f8:0:100:0:0:0:153 nserver: G.DNS.JP 203.119.40.1 nserver: H.DNS.JP 161.232.72.25 2a01:8840:1bc:0:0:0:0:25 ds-rdata: 39916 8 2 b36b524989bf0625efd9b0877e74e77f052248fde965b6e3c327d9c06af1d080 whois: whois.jprs.jp status: ACTIVE remarks: Registration information: https://jprs.jp/ created: 1986-08-05 changed: 2022-11-09 source: IANA
The first response from http://www.sankei.jp, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with sankei.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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.