medecc.org
Its Domain Power Rank is moderate.
- Global Rank
- #353,352
▼ 95,743
- Rank in TLD
- #40,557
▼ 11,440
- Referring Domains
- 269
▼ 8
- Avg. Referrer Power Rank
- 39.3
- Subdomains
- 3
- Domain age
- 10 yr 10 mo
Link Overview
- Avg. Referrer Power Rank
- 39.3
- Median Referrer Power Rank
- 39.2
- Referring Domains
- 269
- Linked Domains
- 553
Referring Domains by Power Rank
0–9 11
10–19 33
20–29 51
30–39 46
40–49 51
50–59 39
60–69 26
70–79 5
80–89 5
90–100 2
Total 269
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| wikipedia.org | 91.8 | #34 |
| europa.eu | 90.5 | #44 |
| weebly.com | 87.4 | #85 |
| substack.com | 84.4 | #173 |
| surveymonkey.com | 82.4 | #288 |
| nasa.gov | 81.1 | #383 |
| mdpi.com | 80.3 | #459 |
| ox.ac.uk | 78.9 | #601 |
| corriere.it | 72.2 | #2,240 |
| cnrs.fr | 71.9 | #2,383 |
Basic Information
- TLD
- .org
- Registration date
- 16 Dec 2015
- Last updated
- 7 Jul 2025
- Expires
- 16 Dec 2026 (42 days remaining)
- Domain statuses
- clientDeleteProhibited clientTransferProhibited
- Registry
- Public Interest Registry (PIR)
- Registrar
- OVH, SAS
Subdomain
next.medecc.orgsurvey.medecc.orgwww.medecc.org
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | medecc.org | 3600 | 5.135.23.164 |
| AAAA | medecc.org | 3600 | 2001:41d0:301::100 |
| MX | medecc.org | 3600 | 1 smtp.osupytheas.fr |
| MX | medecc.org | 3600 | 10 smtp.osupytheas.fr |
| NS | medecc.org | 3600 | ns20.ovh.net |
| NS | medecc.org | 3600 | dns20.ovh.net |
| SOA | medecc.org | 3600 | dns20.ovh.net. tech.ovh.net. 2092548259 86400 3600 3600000 60 |
| TXT | medecc.org | 3600 | 1|www.medecc.org |
| TXT | medecc.org | 3600 | v=spf1 a mx ptr a:medecc.org mx:smtp.osupytheas.fr ptr:smtp.osupytheas.fr ip4:193.50.128.0/24 -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.