numa.jp.net
/.well-known/
resources for
numa.jp.net
Site Scan
Site Details
Site Domain | numa.jp.net |
Base Domain | numa.jp.net |
Added | 2023-01-20T11:11:57+00:00 |
Last Scan | 2024-11-15T13:52:50+00:00 |
Next Scan | 2024-11-29T13:52:50+00:00 |
Found Resources
Resource | Found At | Scan Status |
---|---|---|
apple-app-site-association | 2024-11-15T13:52:50+00:00 | Ok |
Authorized Digital Sellers
Resource Details
Resource | ads.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Authorized Digital Sellers for Apps
Resource Details
Resource | app-ads.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Apple Associated Domain
Resource Details
Resource | apple-app-site-association |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/.well-known/apple-app-site-association |
Result | Not Found - Resource wasn't valid JSON. |
URL | https://numa.jp.net/apple-app-site-association |
Result | Resource Found. |
Last Scan
Scanned | 2024-11-15T13:52:50+00:00 |
URL | https://numa.jp.net/apple-app-site-association |
Domain IPs | 13.35.238.120, 13.35.238.126, 13.35.238.31, 13.35.238.69 |
Response IP | 13.35.238.31 |
Found | Yes - View Resource |
Hash | 1dcc266df27ed5cf7140c67426a057843e28b4c400a32d37d24222edd8c3c8a5 |
SimHash | 775a97c37eb7 |
Digital Asset Links
Resource Details
Resource | assetlinks.json |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/.well-known/assetlinks.json |
Result | Not Found - Resource doesn't exist. |
URL | https://www.numa.jp.net/.well-known/assetlinks.json |
Result | Not Found - Resource doesn't exist. |
Last Scan
Scanned | 2024-11-15T13:52:50+00:00 |
URL | https://numa.jp.net/.well-known/assetlinks.json |
Domain IPs | 13.35.238.120, 13.35.238.126, 13.35.238.31, 13.35.238.69 |
Response IP | 13.35.238.31 |
Found | No |
Not Found Reason | Resource doesn't exist. |
Global Privacy Control
Resource Details
Resource | gpc.json |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/.well-known/gpc.json |
Result | Not Found - Resource doesn't exist. |
URL | https://www.numa.jp.net/.well-known/gpc.json |
Result | Not Found - Resource doesn't exist. |
Last Scan
Scanned | 2024-11-15T13:52:50+00:00 |
URL | https://numa.jp.net/.well-known/gpc.json |
Domain IPs | 13.35.238.120, 13.35.238.126, 13.35.238.31, 13.35.238.69 |
Response IP | 13.35.238.69 |
Found | No |
Not Found Reason | Resource doesn't exist. |
NodeInfo
Resource Details
Resource | nodeinfo |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/.well-known/nodeinfo |
Result | Not Found - Resource wasn't valid JSON. |
URL | https://www.numa.jp.net/.well-known/nodeinfo |
Result | Not Found - Resource wasn't valid JSON. |
Last Scan
Scanned | 2024-11-15T13:52:50+00:00 |
URL | https://numa.jp.net/.well-known/nodeinfo |
Domain IPs | 13.35.238.120, 13.35.238.126, 13.35.238.31, 13.35.238.69 |
Response IP | 13.35.238.31 |
Found | No |
Not Found Reason | Resource wasn't valid JSON. |
OpenID Provider Configuration
Resource Details
Resource | openid-configuration |
Status | Ok |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/.well-known/openid-configuration |
Result | Not Found - Resource wasn't valid JSON. |
URL | https://www.numa.jp.net/.well-known/openid-configuration |
Result | Not Found - Resource wasn't valid JSON. |
Last Scan
Scanned | 2024-11-15T13:52:50+00:00 |
URL | https://numa.jp.net/.well-known/openid-configuration |
Domain IPs | 13.35.238.120, 13.35.238.126, 13.35.238.31, 13.35.238.69 |
Response IP | 13.35.238.31 |
Found | No |
Not Found Reason | Resource wasn't valid JSON. |
Robots Exclusion Standard
Resource Details
Resource | robots.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (2)
URL | https://numa.jp.net/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
security.txt
Resource Details
Resource | security.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://numa.jp.net/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://numa.jp.net/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/.well-known/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/security.txt |
Result | Failed fetching resource - Server returned a client error (403). |
trust.txt
Resource Details
Resource | trust.txt |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://numa.jp.net/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://numa.jp.net/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | https://www.numa.jp.net/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |