irtess.fr
This domain has been registered for many years, but its Domain Power Rank is low.
- Global Rank
- #3,244,784
▲ 595,121
- Rank in TLD
- #50,674
▲ 12,445
- Referring Domains
- 51
▲ 9
- Avg. Referrer Power Rank
- 27.2
- Subdomains
- 2
- Domain age
- 23 yr 4 mo
Link Overview
- Avg. Referrer Power Rank
- 27.2
- Median Referrer Power Rank
- 25.0
- Referring Domains
- 51
- Linked Domains
- 237
Referring Domains by Power Rank
0–9 6
10–19 10
20–29 20
30–39 5
40–49 6
50–59 2
60–69 1
70–79 1
80–89 0
90–100 0
Total 51
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| cnrs.fr | 71.9 | #2,383 |
| hypotheses.org | 67.0 | #5,550 |
| parcoursup.fr | 57.2 | #28,682 |
| ube.fr | 50.4 | #89,664 |
| kh-freiburg.de | 44.8 | #230,972 |
| emfor-bfc.org | 44.4 | #244,867 |
| ash.tm.fr | 43.5 | #282,111 |
| engagement.fr | 43.3 | #289,875 |
| journeeseconomieautrement.fr | 40.7 | #431,781 |
| jeunes-bfc.fr | 40.0 | #479,942 |
Basic Information
Subdomain
netpareo.irtess.frwww.irtess.fr
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | irtess.fr | 3600 | 145.239.37.162 |
| AAAA | irtess.fr | 3600 | 2001:41d0:301::30 |
| MX | irtess.fr | 3600 | 0 irtess-fr.mail.protection.outlook.com |
| NS | irtess.fr | 3600 | ns18.ovh.net |
| NS | irtess.fr | 3600 | dns18.ovh.net |
| SOA | irtess.fr | 3600 | dns18.ovh.net. tech.ovh.net. 2093446524 86400 3600 3600000 60 |
| TXT | irtess.fr | 3600 | 1|www.irtess.fr |
| TXT | irtess.fr | 3600 | MS=3caf00a0-df19-4774-acc3-02c9e792a26f |
| TXT | irtess.fr | 3600 | MS=A2EB179BFE1990A9DE932F95CDFC27F9DBB5BAC8 |
| TXT | irtess.fr | 3600 | v=spf1 include:mx.ovh.com include:spf.protection.outlook.com -all |
| TXT | irtess.fr | 3600 | google-site-verification=PU5gjlwxDQ9vaXZrgMQE83sr61suez9Wrjbpv8xsga8 |
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.