Registered 29 years ago, no valid HTTPS certificate, the site did not answer (OSError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| MX | 1 clone.registro.br 5 fe.registro.br |
|---|---|
| NS | e.dns.br c.dns.br d.dns.br b.dns.br a.dns.br f.dns.br |
| TXT | v=spf1 mx -all |
| registered | 1998-01-20 |
|---|---|
| last changed | 2019-07-31 |
| country | BR |
| nameservers | a.dns.br b.dns.br c.dns.br d.dns.br e.dns.br f.dns.br |
| status | active |
| valid | no |
|---|---|
| problem | Could not resolve host (ENODATA) |
Domain is properly signed — chain validated by an independent validating resolver
| SPF | pass v=spf1 mx -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 dns.br.
Reference: /llms.txt.
IPv6. Does dns.br work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch dns.br. 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