Registered 12 days ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 623 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 198.251.84.236 |
|---|---|
| MX | 10 mail.autowire-tracktransfer.cfd |
| NS | ns113.my-control-panel.com ns114.my-control-panel.com |
| TXT | v=spf1 a mx ip4:198.251.84.236 ip4:198.251.84.236 ~all |
| registrar | Dynadot Inc |
|---|---|
| registered | 2026-10-22 |
| expires | 2027-10-22 |
| last changed | 2026-10-29 |
| owner | Super Privacy Service LTD c/o Dynadot |
| nameservers | ns113.my-control-panel.com ns114.my-control-panel.com |
| status | server transfer prohibited client transfer prohibited transfer prohibited |
| valid | yes |
|---|---|
| issuer | Let's Encrypt |
| covers | *.autowire-tracktransfer.cfd, autowire-tracktransfer.cfd |
| protocol | TLSv1.3 |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 a mx ip4:198.251.84.236 ip4:198.251.84.236 ~all |
|---|---|
| DMARC | none |
| DKIM | none of 1 common selectors |
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 autowire-tracktransfer.cfd.
Reference: /llms.txt.
IPv6. Does autowire-tracktransfer.cfd work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch autowire-tracktransfer.cfd. 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