imst.de
Its Domain Power Rank is moderate.
- Global Rank
- #553,677
▲ 43,192
- Rank in TLD
- #24,729
▲ 3,024
- Referring Domains
- 122
▲ 8
- Avg. Referrer Power Rank
- 31.4
- Subdomains
- 6
- Domain age
- –
Link Overview
- Avg. Referrer Power Rank
- 31.4
- Median Referrer Power Rank
- 26.8
- Referring Domains
- 122
- Linked Domains
- 107
Referring Domains by Power Rank
0–9 8
10–19 34
20–29 27
30–39 24
40–49 10
50–59 7
60–69 5
70–79 4
80–89 1
90–100 2
Total 122
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| github.com | 93.6 | #19 |
| wikipedia.org | 91.8 | #34 |
| mdpi.com | 80.3 | #459 |
| free.fr | 78.2 | #681 |
| zeit.de | 73.9 | #1,570 |
| esa.int | 72.9 | #1,950 |
| kit.edu | 70.5 | #3,092 |
| uni-hannover.de | 68.0 | #4,733 |
| dlr.de | 66.4 | #6,088 |
| uni-bremen.de | 65.7 | #6,686 |
Basic Information
- TLD
- .deGermany
- Last updated
- 20 Mar 2015
- Domain statuses
- active
- Registry
- DENIC eG
Subdomain
cloud.imst.deimst254.imst.deshop.imst.deshopsix.imst.dewebshop.imst.dewww.imst.de
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | imst.de | 600 | 195.243.247.222 |
| MX | imst.de | 3600 | 10 mx0.imst.de |
| MX | imst.de | 3600 | 50 mxbackup.imst.de |
| MX | imst.de | 3600 | 15 mail.imst.de |
| NS | imst.de | 0 | dns2.imst.de |
| NS | imst.de | 0 | dns1.imst.de |
| NS | imst.de | 0 | nsb8.schlundtech.de |
| SOA | imst.de | 3600 | dc4.imst.de. hostmaster.imst.de. 139058 900 600 86400 3600 |
| TXT | imst.de | 3600 | google-site-verification=GReRFTDtSindzCT_6e4jTVbeGZwDp1pMhzuWRVR9hao |
| TXT | imst.de | 3600 | v=spf1 ip4:195.243.247.0/24 ip4:94.79.138.144/29 ip4:81.169.155.164 -all |
| TXT | imst.de | 3600 | sophos-domain-verification=f9ae1635e33ec25672ef7c49951e8a84db85398a775fe0b095e26874d65157c8 |
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.