sbweek.ru
Its Domain Power Rank is moderate.
- Global Rank
- #875,825
▲ 38,627
- Rank in TLD
- #15,831
▲ 1,443
- Referring Domains
- 163
▲ 11
- Avg. Referrer Power Rank
- 27.5
- Subdomains
- 1
- Domain age
- 7 yr 8 mo
Link Overview
- Avg. Referrer Power Rank
- 27.5
- Median Referrer Power Rank
- 25.7
- Referring Domains
- 163
- Linked Domains
- 126
Referring Domains by Power Rank
0–9 12
10–19 39
20–29 46
30–39 37
40–49 19
50–59 6
60–69 3
70–79 1
80–89 0
90–100 0
Total 163
Referring Domains
Basic Information
- TLD
- .ruRussia
- Registration date
- 11 Feb 2019
- Expires
- 11 Feb 2027 (98 days remaining)
- Domain statuses
- REGISTERED DELEGATED UNVERIFIED
- Registry
- Coordination Center for TLD RU
- Registrar
- BEGET-RU
Subdomain
www.sbweek.ru
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | sbweek.ru | 600 | 45.130.41.213 |
| MX | sbweek.ru | 300 | 20 mx2.beget.com |
| MX | sbweek.ru | 300 | 10 mx1.beget.com |
| NS | sbweek.ru | 300 | ns2.beget.ru |
| NS | sbweek.ru | 300 | ns1.beget.ru |
| NS | sbweek.ru | 300 | ns2.beget.pro |
| NS | sbweek.ru | 300 | ns1.beget.pro |
| NS | sbweek.ru | 300 | ns2.beget.com |
| NS | sbweek.ru | 300 | ns1.beget.com |
| SOA | sbweek.ru | 300 | ns1.beget.com. hostmaster.beget.com. 1791580000 300 600 86400 300 |
| TXT | sbweek.ru | 600 | yandex-verification: 7c7d4068d5edb8e6 |
| TXT | sbweek.ru | 300 | mailru-verification: 027f99e81933beac |
| TXT | sbweek.ru | 300 | google-site-verification=bNCsGjo9En-PEtMv_reqZFvNQxyRSp1JcXNgDsdV1U0 |
| TXT | sbweek.ru | 300 | v=spf1 redirect=beget.com |
| TXT | sbweek.ru | 600 | v=spf1 a mx include:spf.smtp.bz ~all |
Email Authentication
- MX
- Valid
- SPF
- Configuration error
Multiple SPF records were found. Only one SPF policy should be published.
- DMARC
- Warning
DMARC is set to p=none, which does not ask receiving servers to quarantine or reject failing messages.
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.