token.kitchen
Its Domain Power Rank is relatively low. Links from multiple referring domains appear in the observed data.
- Global Rank
- #7,903,713
▼ 5,510,179
- Rank in TLD
- #130
▼ 101
- Referring Domains
- 108
▲ 2
- Avg. Referrer Power Rank
- 16.5
- Subdomains
- 0
- Domain age
- –
Link Overview
- Avg. Referrer Power Rank
- 16.5
- Median Referrer Power Rank
- 13.6
- Referring Domains
- 108
- Linked Domains
- 586
Referring Domains by Power Rank
0–9 0
10–19 89
20–29 13
30–39 4
40–49 1
50–59 0
60–69 0
70–79 0
80–89 1
90–100 0
Total 108
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| frontiersin.org | 80.3 | #465 |
| diamandis.com | 48.7 | #121,231 |
| block.science | 39.3 | #530,447 |
| feedbackmagazine.org | 35.9 | #854,111 |
| preface.ai | 35.6 | #889,817 |
| insureblocks.com | 33.9 | #1,192,320 |
| platformcoop.de | 24.9 | #4,836,829 |
| coinerblog.com | 23.4 | #5,913,019 |
| reelnavigator.com | 23.0 | #6,211,848 |
| digitalfinancenews.com | 22.2 | #6,931,368 |
Basic Information
- TLD
- .kitchen
No registration data could be retrieved.
Subdomain
No Observed Data
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | token.kitchen | 3600 | 76.76.21.21 |
| MX | token.kitchen | 3600 | 5 alt1.aspmx.l.google.com |
| MX | token.kitchen | 3600 | 5 alt2.aspmx.l.google.com |
| MX | token.kitchen | 3600 | 10 alt3.aspmx.l.google.com |
| MX | token.kitchen | 3600 | 10 alt4.aspmx.l.google.com |
| MX | token.kitchen | 3600 | 1 aspmx.l.google.com |
| NS | token.kitchen | 3600 | ns65.domaincontrol.com |
| NS | token.kitchen | 3600 | ns66.domaincontrol.com |
| SOA | token.kitchen | 3600 | ns65.domaincontrol.com. dns.jomax.net. 2023052700 28800 7200 604800 600 |
| TXT | token.kitchen | 3600 | v=spf1 include:_spf.google.com ~all |
Email Authentication
- MX
- Valid
- SPF
- Valid
- DMARC
- Not configured
DMARC is not configured.
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.