cap.finance
Its Domain Power Rank is relatively low. Only a small number of referring domains were found in the observed data.
- Global Rank
- #3,715,123
▼ 93,367
- Rank in TLD
- #516
▼ 34
- Referring Domains
- 10
▼ 1
- Avg. Referrer Power Rank
- 34.3
- Subdomains
- 6
- Domain age
- –
Link Overview
- Avg. Referrer Power Rank
- 34.3
- Median Referrer Power Rank
- 26.3
- Referring Domains
- 10
- Linked Domains
- 21
Referring Domains by Power Rank
0–9 1
10–19 3
20–29 2
30–39 1
40–49 1
50–59 1
60–69 0
70–79 0
80–89 0
90–100 1
Total 10
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| github.com | 93.6 | #19 |
| zerion.io | 51.3 | #77,969 |
| tomba.io | 49.6 | #102,733 |
| threesigma.xyz | 34.8 | #1,021,146 |
| hashhub-research.com | 29.6 | #2,371,073 |
| cryptowesearch.com | 22.9 | #6,313,292 |
| leechprotocol.com | 19.6 | #10,307,000 |
| neuy.io | 17.4 | #14,384,252 |
| todayindefi.com | 17.1 | #15,036,282 |
| cap.exchange | 7.0 | #62,500,870 |
Basic Information
- TLD
- .finance
No registration data could be retrieved.
Subdomain
blog.cap.financedocs.cap.financev1.cap.financev2.cap.financev31.cap.financewww.cap.finance
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | cap.finance | 1385 | 162.255.119.78 |
| MX | cap.finance | 1799 | 10 mail.protonmail.ch |
| MX | cap.finance | 1799 | 20 mailsec.protonmail.ch |
| NS | cap.finance | 1800 | pdns1.registrar-servers.com |
| NS | cap.finance | 1800 | pdns2.registrar-servers.com |
| SOA | cap.finance | 3601 | pdns1.registrar-servers.com. hostmaster.registrar-servers.com. 1693324282 43200 3600 604800 3601 |
| TXT | cap.finance | 1799 | v=spf1 include:_spf.protonmail.ch mx ~all |
| TXT | cap.finance | 1799 | protonmail-verification=a04920cf05f8a65784b603586cbf5902563718a3 |
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.