ticketservice.nl
/.well-known/
resources for
ticketservice.nl
Site Scan
Site Details
| Site Domain | ticketservice.nl |
| Base Domain | ticketservice.nl |
| Added | 2021-03-12T15:36:19+00:00 |
| Last Scan | 2024-10-08T14:36:39+00:00 |
| Next Scan | 2025-01-06T14:36:39+00:00 |
Found Resources
| Resource | Found At | Scan Status |
|---|---|---|
| ads.txt | 2024-06-11T14:13:30+00:00 | Failed |
| robots.txt | 2024-06-11T14:13:30+00:00 | Failed |
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://ticketservice.nl/ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2024-06-11T14:13:30+00:00 |
| URL | http://ticketservice.nl/ads.txt |
| Redirect | https://www.ticketmaster.nl/ads.txt |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Domain IPs | 151.101.0.204, 151.101.128.204, 151.101.192.204, 151.101.64.204 |
| Redirect IPs | 151.101.1.237, 151.101.129.237, 151.101.193.237, 151.101.65.237 |
| Response IP | 199.232.45.237 |
| Found | Yes - View Resource |
| Hash | f07f9ee41dbe0fb03e1c2f839a026151c70274bf0db2654b69970c57c34b5155 |
| SimHash | c8748990666b |
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://ticketservice.nl/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/app-ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/app-ads.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2024-06-11T14:13:30+00:00 |
| URL | http://ticketservice.nl/app-ads.txt |
| Redirect | https://www.ticketmaster.nl/app-ads.txt |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Domain IPs | 151.101.0.204, 151.101.128.204, 151.101.192.204, 151.101.64.204 |
| Redirect IPs | 151.101.1.237, 151.101.129.237, 151.101.193.237, 151.101.65.237 |
| Response IP | 199.232.45.237 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |
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://ticketservice.nl/.well-known/apple-app-site-association |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/apple-app-site-association |
| Result | Failed checking robots.txt - Couldn't connect to server. |
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://ticketservice.nl/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/.well-known/assetlinks.json |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/.well-known/assetlinks.json |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2022-09-17T03:03:25+00:00 |
| URL | http://ticketservice.nl/.well-known/assetlinks.json |
| Redirect | https://www.ticketmaster.nl/.well-known/assetlinks.json |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Response IP | 199.232.46.87 |
| Found | No |
| Not Found Reason | Request was redirected to another domain. |
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://ticketservice.nl/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/.well-known/gpc.json |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/.well-known/gpc.json |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2022-09-17T03:03:25+00:00 |
| URL | http://ticketservice.nl/.well-known/gpc.json |
| Redirect | https://www.ticketmaster.nl/.well-known/gpc.json |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Response IP | 199.232.46.87 |
| Found | No |
| Not Found Reason | Server returned a client error. |
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://ticketservice.nl/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/.well-known/nodeinfo |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/.well-known/nodeinfo |
| Result | Failed fetching resource - Server returned a client error (403). |
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://ticketservice.nl/.well-known/openid-configuration |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/openid-configuration |
| Result | Failed checking robots.txt - Couldn't connect to server. |
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://ticketservice.nl/robots.txt |
| Result | Failed fetching resource - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/robots.txt |
| Result | Failed fetching resource - Couldn't connect to server. |
| URL | http://ticketservice.nl/robots.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/robots.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2024-06-11T14:13:30+00:00 |
| URL | http://ticketservice.nl/robots.txt |
| Redirect | https://www.ticketmaster.nl/robots.txt |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Domain IPs | 151.101.0.204, 151.101.128.204, 151.101.192.204, 151.101.64.204 |
| Redirect IPs | 151.101.1.237, 151.101.129.237, 151.101.193.237, 151.101.65.237 |
| Response IP | 199.232.45.237 |
| Found | Yes - View Resource |
| Hash | e94dd6841bc1cd08822db22693d983d28abcf94080fecc827542f97ff129c5fc |
| SimHash | 8474b4607555 |
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://ticketservice.nl/.well-known/security.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/security.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
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://ticketservice.nl/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.ticketservice.nl/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://ticketservice.nl/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://ticketservice.nl/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
| URL | http://www.ticketservice.nl/trust.txt |
| Result | Failed fetching resource - Server returned a client error (403). |
Last Successful Scan
| Scanned | 2024-06-11T14:13:30+00:00 |
| URL | http://ticketservice.nl/.well-known/trust.txt |
| Redirect | https://www.ticketmaster.nl/.well-known/trust.txt |
| Redirect Domain | www.ticketmaster.nl |
| Redirect Base | ticketmaster.nl |
| Domain IPs | 151.101.0.204, 151.101.128.204, 151.101.192.204, 151.101.64.204 |
| Redirect IPs | 151.101.1.237, 151.101.129.237, 151.101.193.237, 151.101.65.237 |
| Response IP | 199.232.45.237 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |