scheduling.com
/.well-known/
resources for
scheduling.com
Site Scan
Site Details
| Site Domain | scheduling.com |
| Base Domain | scheduling.com |
| Added | 2021-08-03T10:42:49+00:00 |
| Last Scan | 2024-04-08T23:48:23+00:00 |
| Next Scan | 2024-07-07T23:48:23+00:00 |
Found Resources
| Resource | Found At | Scan Status |
|---|---|---|
| robots.txt | 2023-08-17T07:25:20+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://scheduling.com/ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/ads.txt |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/ads.txt |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/ads.txt |
| Redirect | https://www.r1rcm.com/ads.txt |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.2 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |
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://scheduling.com/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/app-ads.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/app-ads.txt |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/app-ads.txt |
| Redirect | https://www.r1rcm.com/app-ads.txt |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.2 |
| 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://scheduling.com/.well-known/apple-app-site-association |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/apple-app-site-association |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
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://scheduling.com/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/.well-known/assetlinks.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/.well-known/assetlinks.json |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/.well-known/assetlinks.json |
| Redirect | https://www.r1rcm.com/.well-known/assetlinks.json |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.2 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |
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://scheduling.com/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/.well-known/gpc.json |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/.well-known/gpc.json |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/.well-known/gpc.json |
| Redirect | https://www.r1rcm.com/.well-known/gpc.json |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.254 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |
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://scheduling.com/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/.well-known/nodeinfo |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/.well-known/nodeinfo |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/.well-known/nodeinfo |
| Redirect | https://www.r1rcm.com/.well-known/nodeinfo |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.2 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |
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://scheduling.com/.well-known/openid-configuration |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/openid-configuration |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
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://scheduling.com/robots.txt |
| Result | Failed fetching resource - Couldn't connect to server. |
| URL | https://www.scheduling.com/robots.txt |
| Result | Failed fetching resource - Couldn't establish SSL connection. |
| URL | http://scheduling.com/robots.txt |
| Result | Failed fetching resource - Couldn't connect to server. |
| URL | http://www.scheduling.com/robots.txt |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/robots.txt |
| Redirect | https://scisolutions.com/robots.txt |
| Redirect Domain | scisolutions.com |
| Redirect Base | scisolutions.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.129, 199.60.103.29 |
| Response IP | 199.60.103.129 |
| Found | Yes - View Resource |
| Hash | 76febf0c34a6106fa4cca9e058a507e3c35db82d4ac904b354cdb3d2bac4f15e |
| SimHash | 7455d6a8eeb3 |
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://scheduling.com/.well-known/security.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/security.txt |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
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 (5)
| URL | https://scheduling.com/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | https://www.scheduling.com/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't establish SSL connection. |
| URL | http://scheduling.com/.well-known/trust.txt |
| Result | Failed checking robots.txt - Couldn't connect to server. |
| URL | http://www.scheduling.com/.well-known/trust.txt |
| Result | Failed fetching resource - Server returned a client error (409). |
| URL | http://www.scheduling.com/trust.txt |
| Result | Failed fetching resource - Server returned a client error (409). |
Last Successful Scan
| Scanned | 2023-08-17T07:25:20+00:00 |
| URL | http://www.scheduling.com/.well-known/trust.txt |
| Redirect | https://www.r1rcm.com/.well-known/trust.txt |
| Redirect Domain | www.r1rcm.com |
| Redirect Base | r1rcm.com |
| Domain IPs | 72.10.51.192 |
| Redirect IPs | 199.60.103.2, 199.60.103.254, 2606:2c40::c73c:6702, 2606:2c40::c73c:67fe |
| Response IP | 199.60.103.2 |
| Found | No |
| Not Found Reason | Resource doesn't exist. |