Registered 13 years ago, on no blocklists we checked, no valid HTTPS certificate, the site did not answer (timed out).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| A | 158.160.26.16 |
|---|---|
| MX | 10 mx.yandex.net |
| NS | ns2.otm-r.com ns6.otm-r.com ns3.otm-r.com ns5.otm-r.com |
| TXT | v=spf1 redirect=_spf.yandex.net google-site-verification=k3WDVTk5K51yF-SS2kR85Q5MzSd1KzGkssvrFGKkF7E yandex-verification: 47f0f76734530a54 |
| registrar | Registrar of Domain Names REG.RU LLC |
|---|---|
| registered | 2014-01-16 |
| expires | 2027-01-16 |
| last changed | 2026-10-12 |
| nameservers | ns3.otm-r.com ns5.otm-r.com ns6.otm-r.com |
| status | client transfer prohibited |
| valid | no |
|---|---|
| problem | Connection timed out |
Domain is not signed with DNSSEC
| SPF | warning v=spf1 redirect=_spf.yandex.net |
|---|---|
| DMARC | pass policy reject |
| DKIM | found: mail |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on otm-r.com.
Reference: /llms.txt.
IPv6. Does otm-r.com work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch otm-r.com. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days