ecrivain-e.com
Its Domain Power Rank is relatively low.
- Global Rank
- #19,369,581
▲ 3,117,682
- Rank in TLD
- #8,431,885
▲ 1,392,664
- Referring Domains
- 7
▲ 1
- Avg. Referrer Power Rank
- 20.8
- Subdomains
- 1
- Domain age
- 7 yr 9 mo
Link Overview
- Avg. Referrer Power Rank
- 20.8
- Median Referrer Power Rank
- 18.3
- Referring Domains
- 7
- Linked Domains
- 142
Referring Domains by Power Rank
0–9 1
10–19 5
20–29 0
30–39 0
40–49 0
50–59 1
60–69 0
70–79 0
80–89 0
90–100 0
Total 7
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| stevenpressfield.com | 52.6 | #62,002 |
| happynaiss.com | 19.6 | #10,447,806 |
| plumebis.ch | 18.6 | #12,207,543 |
| lesamesdabord.ch | 18.3 | #12,837,549 |
| isabelleaeschlimann.ch | 16.3 | #16,824,527 |
| fannygayral.com | 12.6 | #27,601,912 |
| matyldahagmajer.com | 7.4 | #58,442,215 |
Basic Information
- TLD
- .com
- Registration date
- 29 Jan 2019
- Last updated
- 30 Jan 2025
- Expires
- 29 Jan 2027 (85 days remaining)
- Domain statuses
- clientDeleteProhibited clientTransferProhibited
- Registry
- VeriSign Global Registry Services
- Registrar
- OVH, SAS
Subdomain
www.ecrivain-e.com
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | ecrivain-e.com | 3600 | 92.222.139.190 |
| AAAA | ecrivain-e.com | 3600 | 2001:41d0:301:3::28 |
| MX | ecrivain-e.com | 3600 | 1 mx1.mail.ovh.net |
| MX | ecrivain-e.com | 3600 | 5 mx2.mail.ovh.net |
| MX | ecrivain-e.com | 3600 | 100 mx3.mail.ovh.net |
| NS | ecrivain-e.com | 3600 | ns109.ovh.net |
| NS | ecrivain-e.com | 3600 | dns109.ovh.net |
| SOA | ecrivain-e.com | 3600 | dns109.ovh.net. tech.ovh.net. 2091669802 86400 3600 3600000 60 |
| TXT | ecrivain-e.com | 3600 | 1|www.ecrivain-e.com |
| TXT | ecrivain-e.com | 3600 | v=spf1 include:mx.ovh.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.