magazinmatik.com
/.well-known/
resources for
magazinmatik.com
Site Scan
Site Details
Site Domain | magazinmatik.com |
Base Domain | magazinmatik.com |
Added | 2021-06-10T22:15:33+00:00 |
Last Scan | 2024-09-03T13:38:56+00:00 |
Next Scan | 2024-12-02T13:38:56+00:00 |
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 (4)
URL | https://magazinmatik.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/ads.txt |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource didn't match the expected format. |
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 (4)
URL | https://magazinmatik.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/app-ads.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/app-ads.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/app-ads.txt |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource didn't match the expected format. |
Apple Associated Domain
Resource Details
Resource | apple-app-site-association |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://magazinmatik.com/.well-known/apple-app-site-association |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/apple-app-site-association |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2023-09-27T11:50:53+00:00 |
URL | https://magazinmatik.com/.well-known/apple-app-site-association |
Redirect | https://www.magazinmatik.com/.well-known/apple-app-site-association |
Redirect Domain | www.magazinmatik.com |
Redirect Base | magazinmatik.com |
Domain IPs | 185.33.233.146 |
Redirect IPs | 185.33.233.146 |
Response IP | 185.33.233.146 |
Found | No |
Not Found Reason | Resource doesn't exist. |
Digital Asset Links
Resource Details
Resource | assetlinks.json |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://magazinmatik.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/assetlinks.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/.well-known/assetlinks.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/.well-known/assetlinks.json |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource wasn't valid JSON. |
Global Privacy Control
Resource Details
Resource | gpc.json |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://magazinmatik.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/gpc.json |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/.well-known/gpc.json |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/.well-known/gpc.json |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource was too long. |
NodeInfo
Resource Details
Resource | nodeinfo |
Status | Failed |
Failure Stage | Fetching resource. |
Failure Reason | Server returned a client error. |
Archive | Check Archive |
Scan Requests (4)
URL | https://magazinmatik.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/nodeinfo |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/.well-known/nodeinfo |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/.well-known/nodeinfo |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource was too long. |
OpenID Provider Configuration
Resource Details
Resource | openid-configuration |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://magazinmatik.com/.well-known/openid-configuration |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/openid-configuration |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2023-09-27T11:50:53+00:00 |
URL | https://magazinmatik.com/.well-known/openid-configuration |
Redirect | https://www.magazinmatik.com/.well-known/openid-configuration |
Redirect Domain | www.magazinmatik.com |
Redirect Base | magazinmatik.com |
Domain IPs | 185.33.233.146 |
Redirect IPs | 185.33.233.146 |
Response IP | 185.33.233.146 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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 (4)
URL | https://magazinmatik.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | https://www.magazinmatik.com/robots.txt |
Result | Failed fetching resource - Couldn't connect to server. |
URL | http://magazinmatik.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/robots.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/robots.txt |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource didn't match the expected format. |
security.txt
Resource Details
Resource | security.txt |
Status | Failed |
Failure Stage | Checking robots.txt. |
Failure Reason | Couldn't connect to server. |
Archive | Check Archive |
Scan Requests (2)
URL | https://magazinmatik.com/.well-known/security.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/security.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
Last Successful Scan
Scanned | 2023-09-27T11:50:53+00:00 |
URL | https://magazinmatik.com/.well-known/security.txt |
Redirect | https://www.magazinmatik.com/.well-known/security.txt |
Redirect Domain | www.magazinmatik.com |
Redirect Base | magazinmatik.com |
Domain IPs | 185.33.233.146 |
Redirect IPs | 185.33.233.146 |
Response IP | 185.33.233.146 |
Found | No |
Not Found Reason | Resource doesn't exist. |
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 (6)
URL | https://magazinmatik.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | https://www.magazinmatik.com/.well-known/trust.txt |
Result | Failed checking robots.txt - Couldn't connect to server. |
URL | http://magazinmatik.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://magazinmatik.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/.well-known/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
URL | http://www.magazinmatik.com/trust.txt |
Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
Scanned | 2023-11-09T12:48:52+00:00 |
URL | http://magazinmatik.com/.well-known/trust.txt |
Redirect | http://magazinmatik.com/ |
Domain IPs | 31.207.83.53 |
Response IP | 31.207.83.53 |
Found | No |
Not Found Reason | Resource didn't match the expected format. |