tokenforum.ru
Its Domain Power Rank is relatively low.
- Global Rank
- #6,760,682
▲ 1,100,384
- Rank in TLD
- #152,094
▲ 29,690
- Referring Domains
- 38
▲ 8
- Avg. Referrer Power Rank
- 22.5
- Subdomains
- 0
- Domain age
- 4 yr 2 mo
Link Overview
- Avg. Referrer Power Rank
- 22.5
- Median Referrer Power Rank
- 17.9
- Referring Domains
- 38
- Linked Domains
- 440
Referring Domains by Power Rank
0–9 3
10–19 19
20–29 6
30–39 7
40–49 2
50–59 1
60–69 0
70–79 0
80–89 0
90–100 0
Total 38
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| bits.media | 52.6 | #61,845 |
| kurs.expert | 49.4 | #105,796 |
| mem168new.com | 47.3 | #153,983 |
| forumonly.fun | 39.3 | #529,576 |
| marqly.com | 38.2 | #620,832 |
| comcash.cc | 37.0 | #723,080 |
| 1ha.ru | 35.3 | #946,348 |
| secrex.io | 31.6 | #1,712,644 |
| groszek.katowice.pl | 31.2 | #1,837,253 |
| finforums.ru | 30.3 | #2,105,728 |
Basic Information
- TLD
- .ruRussia
- Registration date
- 10 Aug 2022
- Expires
- 10 Aug 2027 (278 days remaining)
- Domain statuses
- REGISTERED DELEGATED UNVERIFIED
- Registry
- Coordination Center for TLD RU
- Registrar
- REGRU-RU
Subdomain
No data
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | tokenforum.ru | 600 | 87.236.21.135 |
| MX | tokenforum.ru | 300 | 20 mx2.beget.com |
| MX | tokenforum.ru | 300 | 10 mx1.beget.com |
| NS | tokenforum.ru | 300 | ns2.beget.ru |
| NS | tokenforum.ru | 300 | ns1.beget.ru |
| NS | tokenforum.ru | 300 | ns2.beget.pro |
| NS | tokenforum.ru | 300 | ns1.beget.pro |
| NS | tokenforum.ru | 300 | ns2.beget.com |
| NS | tokenforum.ru | 300 | ns1.beget.com |
| SOA | tokenforum.ru | 300 | ns1.beget.com. hostmaster.beget.com. 1693223119 300 600 86400 300 |
| TXT | tokenforum.ru | 300 | v=spf1 redirect=beget.com |
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.