Registered 27 years ago, no valid HTTPS certificate, the site did not answer (OSError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| MX | 10 mx-att.mail.am0.yahoodns.net |
|---|---|
| NS | a5-67.akam.net a14-65.akam.net a4-66.akam.net a8-64.akam.net a9-66.akam.net a1-212.akam.net |
| TXT | v=spf1 include:_ipspf.yahoo.com ~all |
| registrar | CSC Corporate Domains, Inc. |
|---|---|
| registered | 2000-03-27 |
| expires | 2027-03-27 |
| last changed | 2026-03-23 |
| owner | AT&T SERVICES, INC. |
| nameservers | a1-212.akam.net a14-65.akam.net a4-66.akam.net a5-67.akam.net a8-64.akam.net a9-66.akam.net |
| status | client transfer prohibited server delete prohibited server transfer prohibited server update prohibited |
| valid | no |
|---|---|
| problem | Could not resolve host (ENODATA) |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 include:_ipspf.yahoo.com ~all |
|---|---|
| DMARC | pass policy reject |
| 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 sbcglobal.net.
Reference: /llms.txt.
IPv6. Does sbcglobal.net work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch sbcglobal.net. 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