api.shingaku.jp
2600:140b:6c00:7e::17c7:385e
Public Scan
Open in
urlscan Pro
http://api.shingaku.jp/ 6mo old
Effective URL:
https://api.shingaku.jp/ 6mo old
Submission: On August 25 via api (August 25th 2026, 7:21:30 pm UTC) from KR — Scanned from JP Go Pro
Only in urlscan Pro
- Select different country locations for Private Scans.
- Use a global network of additional scanning locations and residential IPs for scanning.
- Interact with pages while you are scanning them.
- Download files from remote websites.
- Scan websites on the Tor Network.
Summary
TLS certificate: Issued by DigiCert Global G3 TLS ECC SHA384 202... on April 14th 2026. Valid for: 7mo.
This is the only time api.shingaku.jp was scanned on urlscan.io!
urlscan.io Verdict: No classification
Domain & IP information
| IP Address | AS Autonomous System | ||
|---|---|---|---|
| 2 | 2600:140b:6c0... 2600:140b:6c00:7e::17c7:385e | 20940 (AKAMAI-AS...) (AKAMAI-ASN1 Akamai International B.V.) | |
| 2 | 1 |
ASN20940 (AKAMAI-ASN1 Akamai International B.V., NL)
| api.shingaku.jp 6mo old |
| Apex Domain Subdomains |
Transfer | |
|---|---|---|
| 2 |
shingaku.jp
api.shingaku.jp 6mo old |
2 KB |
| 2 | 1 |
| Domain | Requested by | |
|---|---|---|
| 2 | api.shingaku.jp | |
| 2 | 1 |
This site contains no links.
| Subject Issuer | Validity | Valid | |
|---|---|---|---|
| shingaku.jp DigiCert Global G3 TLS ECC SHA384 2020 CA1 |
2026-04-14 - 2026-10-29 |
7mo | crt.sh |
This page contains 1 frames:
Primary Page:
https://api.shingaku.jp/
Frame ID: FB8002823D909ACB3D717C05FC98450B
Requests: 2 HTTP requests in this frame
Screenshot
Go Pro
Only in urlscan Pro
Use the Visual Search feature to find pages with visually similar screenshots.
Click for more information
Free trials of urlscan Pro are available.
Page URL History
Go Pro
Only in urlscan Pro
Search our real-time database of newly observed domains and
hostnames. Pivot on different attributes, and setup keyword alerts for
newly observed domains.
Click for more information
Free trials of urlscan Pro are available.
Show full URLs
-
http://api.shingaku.jp/
HTTP 307
https://api.shingaku.jp/ Page URL
Page Statistics
0 Outgoing links
These are links going to different origins than the main page.
Page URL History
This captures the URL locations of the websites, including HTTP redirects and client-side redirects via JavaScript or Meta fields.
-
http://api.shingaku.jp/
HTTP 307
https://api.shingaku.jp/ Page URL
Redirected requests
There were HTTP redirect chains for the following requests:
2 HTTP transactions
0 data transactions
| Method Protocol |
Status | Resource Path |
Size x-fer |
Time Latency |
Type MIME-Type |
IP Location |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
GET H2 |
401 |
Primary Request
/
Show response
api.shingaku.jp/ Redirect Chain
|
125 B 792 B |
143ms
126ms |
Document
application/json |
2600:140b:6c00:7e::17c7:385e AKAMAI-ASN1 Akama... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
General
Request headers
Response headers
Redirect headers
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
GET H2 |
401 |
favicon.ico
api.shingaku.jp/ |
125 B 788 B |
48ms
47ms |
Other
application/json |
2600:140b:6c00:7e::17c7:385e AKAMAI-ASN1 Akama... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
General
Request headers
Response headers
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Verdicts & Comments Add Verdict or Comment
0 JavaScript Window variables
These are the non-standard variables defined on the window object. These include var declarations and global functions and can be helpful in identifying possible client-side frameworks and code.
0 Cookies
Cookies are little pieces of information stored in the browser of a user. Whenever a user visits the site again, he will also send his cookie values, thus allowing the website to re-identify him even if he changed locations. This is how permanent logins work.
2 Console Messages
A page may trigger messages to the console to be logged. These are often error messages about being unable to load a resource or execute a piece of JavaScript. Sometimes they also provide insight into the technology behind a website.
| Source | Level | URL Text |
|---|
Security Headers
This page lists any security headers set by the main page. If you want to understand what these mean and how to use them, head on over to this page
| Header | Value |
|---|---|
| Content-Security-Policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; connect-src 'self' https://api.aws2.shingaku.jp https://api-internal.shingaku.jp https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src https://*.googletagmanager.com; frame-ancestors 'none' |
| Strict-Transport-Security | max-age=15768000 |
| X-Content-Type-Options | nosniff |
| X-Frame-Options | DENY |
Indicators
This is a term in the security industry to describe indicators such as IPs, Domains, Hashes, etc. This does not imply that any of these indicate malicious activity.
api.shingaku.jp
2600:140b:6c00:7e::17c7:385e
205553069129994089b217d083938a69c69399c2a15d24640e4b4fe98a04d885
2bbf76fa05d9295c9aa8e8674473baf7bc137acefed117ed4955b34095e1317d