vitalchek.com
Its Domain Power Rank is relatively high.
- Global Rank
- #16,350
▲ 40,964
- Rank in TLD
- #7,713
▲ 17,662
- Referring Domains
- 1,040
▼ 4
- Avg. Referrer Power Rank
- 29.4
- Subdomains
- 11
- Domain age
- 31 yr 2 mo
Link Overview
- Avg. Referrer Power Rank
- 29.4
- Median Referrer Power Rank
- 26.7
- Referring Domains
- 1,040
- Linked Domains
- 362
Referring Domains by Power Rank
0–9 135
10–19 215
20–29 252
30–39 169
40–49 135
50–59 64
60–69 28
70–79 37
80–89 3
90–100 2
Total 1,040
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| google.com | 99.8 | #1 |
| squarespace.com | 90.3 | #46 |
| outlook.com | 86.2 | #119 |
| ca.gov | 83.6 | #211 |
| eloqua.com | 83.1 | #253 |
| house.gov | 78.6 | #645 |
| ny.gov | 78.1 | #695 |
| wisc.edu | 77.3 | #812 |
| nyc.gov | 76.8 | #903 |
| wa.gov | 76.6 | #939 |
Basic Information
- TLD
- .com
- Registration date
- 22 Aug 1995
- Last updated
- 10 Nov 2023
- Expires
- 21 Aug 2030 (1,385 days remaining)
- Domain statuses
- clientTransferProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- Network Solutions, LLC
Subdomain
blog.vitalchek.comcustomers.vitalchek.comuat.daveaz.vitalchek.comdavenc.vitalchek.comdaveok.vitalchek.comdavewv.vitalchek.comuat.davewv.vitalchek.comfuneralhome.vitalchek.comlacstorefront.vitalchek.comohstorefront.vitalchek.comwww.vitalchek.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | vitalchek.com | 300 | 69.84.183.237 |
| MX | vitalchek.com | 60 | 10 vitalchek-com.mail.protection.outlook.com |
| NS | vitalchek.com | 86400 | max.ns.cloudflare.com |
| NS | vitalchek.com | 86400 | mary.ns.cloudflare.com |
| SOA | vitalchek.com | 1800 | mary.ns.cloudflare.com. dns.cloudflare.com. 2419304655 10000 2400 604800 1800 |
| TXT | vitalchek.com | 60 | MS=ms91176924 |
| TXT | vitalchek.com | 60 | ea558ab404a34fe896a064e8a9e846bc |
| TXT | vitalchek.com | 60 | jamf-site-verification=8MIO9ebUo7teSBoypzXWfQ |
| TXT | vitalchek.com | 60 | nitro-verification-code=NzMxOTIyNTU3Njc0MDk1NDA5Nw== |
| TXT | vitalchek.com | 60 | docker-verification=6b9b6a18-7d07-408a-a832-928642e38cc5 |
| TXT | vitalchek.com | 60 | miro-verification=3d2363e884567e60ec283b191ae2c9ce99a3f4e0 |
| TXT | vitalchek.com | 60 | onetrust-domain-verification=4d3fcbf3fde846c08ffa5b296c2a6359 |
| TXT | vitalchek.com | 60 | webexdomainverification.=19df3bb0-669b-4407-bf4d-02e575ca9b78 |
| TXT | vitalchek.com | 60 | _globalsign-domain-verification=wpSMzX_6iVFbEXoQlUIP9QCndYnKfZtRl9zN7xhnOn |
| TXT | vitalchek.com | 60 | tOBeJiOhzZUybq4g3yRc7HRHinD/UjnVfMl6kxPD4SzreYFeHWzjPtdM91RuK+iJHmBx9iXh6VIkEUWJdpIXvg== |
| TXT | vitalchek.com | 60 | infoblox-domain-mastery=ddf124fcd46f49bfc48a03af3528a75dbca8802393a74d85c697fe70e4984f8cc7 |
| TXT | vitalchek.com | 60 | atlassian-domain-verification=zllkkKudgPvT7s5hJjK9ghYfKXIapy8zXLOGOO/TiEXfT568cSDvw3aZu/gsvx/e |
| TXT | vitalchek.com | 60 | v=spf1 ip4:66.241.37.182/32 ip4:12.38.207.30/32 ip4:216.133.255.171/32 ip4:34.252.159.188/32 ip4:198.185.18.9/32 ip4:198.185.18.10/32 include:_netblocks.eloqua.com include:_spf.qualtrics.com include:spf.protection.outlook.com include:highspot.vitalchek.com include:spfrecord.lexisnexisrisk.com -all |
| CAA | vitalchek.com | 300 | 0 issue "comodoca.com" |
| CAA | vitalchek.com | 300 | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| CAA | vitalchek.com | 300 | 0 issue "globalsign.com" |
| CAA | vitalchek.com | 300 | 0 issue "letsencrypt.org" |
| CAA | vitalchek.com | 300 | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| CAA | vitalchek.com | 300 | 0 issue "ssl.com" |
| CAA | vitalchek.com | 300 | 0 issue "vikingcloud.com" |
| CAA | vitalchek.com | 300 | 0 issuewild "comodoca.com" |
| CAA | vitalchek.com | 300 | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| CAA | vitalchek.com | 300 | 0 issuewild "letsencrypt.org" |
| CAA | vitalchek.com | 300 | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| CAA | vitalchek.com | 300 | 0 issuewild "ssl.com" |
Email Authentication
- MX
- Valid
- SPF
- Valid
- DMARC
- Valid
DMARC is set to p=reject, asking receiving servers to reject messages that fail authentication.
Some information is cached or comes from our own analysis, so it may not be current or complete. Our link analysis does not cover every link on the web. Metrics are based on our own methodology and should not be taken as definitive assessments of a domain’s or service’s quality or trustworthiness.