testim.io
Its Domain Power Rank is relatively high.
- Global Rank
- #62,661
▲ 18,737
- Rank in TLD
- #1,624
▲ 410
- Referring Domains
- 779
▲ 7
- Avg. Referrer Power Rank
- 32.4
- Subdomains
- 9
- Domain age
- 12 yr 2 mo
Link Overview
- Avg. Referrer Power Rank
- 32.4
- Median Referrer Power Rank
- 30.1
- Referring Domains
- 779
- Linked Domains
- 324
Referring Domains by Power Rank
0–9 78
10–19 140
20–29 167
30–39 143
40–49 125
50–59 63
60–69 38
70–79 15
80–89 9
90–100 1
Total 779
Referring Domains
| Referring domain | Power Rank | Global Rank |
|---|---|---|
| google.com | 99.8 | #1 |
| hubspot.com | 85.5 | #139 |
| wikimedia.org | 85.2 | #150 |
| substack.com | 84.4 | #173 |
| hostinger.com | 84.1 | #188 |
| arxiv.org | 83.9 | #197 |
| salesforce.com | 83.6 | #216 |
| atlassian.com | 82.7 | #271 |
| elementor.com | 81.0 | #388 |
| meetup.com | 80.7 | #418 |
Basic Information
- Registration date
- 27 Aug 2014
- Last updated
- 11 Aug 2026
- Expires
- 27 Aug 2027 (295 days remaining)
- Domain statuses
- clientTransferProhibited
- Registry
- Internet Computer Bureau Limited
- Registrar
- Cloudflare, Inc
Subdomain
app.testim.ioblog.testim.iocommunity.testim.iodemo.testim.iodocs.testim.iogo.testim.iohelp.testim.ioresources.testim.iowww.testim.io
DNS
| Type | Name | TTL | Value |
|---|---|---|---|
| A | testim.io | 300 | 104.18.13.227 |
| A | testim.io | 300 | 104.18.12.227 |
| AAAA | testim.io | 300 | 2606:4700::6812:ce3 |
| AAAA | testim.io | 300 | 2606:4700::6812:de3 |
| MX | testim.io | 300 | 10 mxa-00980101.gslb.pphosted.com |
| MX | testim.io | 300 | 10 mxb-00980101.gslb.pphosted.com |
| NS | testim.io | 81140 | anuj.ns.cloudflare.com |
| NS | testim.io | 81140 | uma.ns.cloudflare.com |
| SOA | testim.io | 1800 | anuj.ns.cloudflare.com. dns.cloudflare.com. 2418964124 10000 2400 604800 1800 |
| TXT | testim.io | 300 | MS=ms16666387 |
| TXT | testim.io | 300 | MS=ms96991469 |
| TXT | testim.io | 300 | adobe-idp-site-verification=a6547714d9b648131d82c98c3196ebb4dca9f6009ec2b32fb75394743338a150 |
| TXT | testim.io | 300 | firebase=blinding-heat-7022 |
| TXT | testim.io | 300 | globalsign-domain-verification=zWPU60YFQ0yGYYzxisvoXHgatL_-vEWm_fmAqeVOU6 |
| TXT | testim.io | 300 | google-site-verification=28CkuybFtwrVAMpt0VNk2iI5Ec6WhXbT24F_WG-EKi8 |
| TXT | testim.io | 300 | google-site-verification=FXTh2vKAOfeS_buKJ_gvBjUb_z6IQ9YwgPbFWMwR6m8 |
| TXT | testim.io | 300 | google-site-verification=OP7LxcgFXzYUbQIkvcIodq_36qAmxpVo4Dq9RPGgrtE |
| TXT | testim.io | 300 | google-site-verification=otkJ5_WZOp2AimyvxxBrWL3vLIW4LoK90liW66kXw0U |
| TXT | testim.io | 300 | slack-domain-verification=w1y5npSdWmAC9w8gQ50Hjh8lnYZf1bUxU50BuOXd |
| TXT | testim.io | 300 | unbounce 226928 |
| TXT | testim.io | 300 | v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all |
| CAA | testim.io | 300 | 0 iodef "mailto: alerts@testim.io" |
| CAA | testim.io | 300 | 0 issue "amazon.com" |
| CAA | testim.io | 300 | 0 issue "comodoca.com" |
| CAA | testim.io | 300 | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| CAA | testim.io | 300 | 0 issue "letsencrypt.org" |
| CAA | testim.io | 300 | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| CAA | testim.io | 300 | 0 issue "ssl.com" |
| CAA | testim.io | 300 | 0 issue "text box: sectigo.com" |
| CAA | testim.io | 300 | 0 issuewild "amazon.com" |
| CAA | testim.io | 300 | 0 issuewild "comodoca.com" |
| CAA | testim.io | 300 | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| CAA | testim.io | 300 | 0 issuewild "letsencrypt.org" |
| CAA | testim.io | 300 | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| CAA | testim.io | 300 | 0 issuewild "ssl.com" |
| CAA | testim.io | 300 | 0 issuewild "text box: sectigo.com" |
Email Authentication
- MX
- Valid
- SPF
- Warning
The SPF check could not be completed because of too many DNS references or macros.
- DMARC
- Valid
DMARC is set to p=reject, asking receiving servers to reject messages that fail authentication.
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.