On no blocklists we checked, valid HTTPS, the site answered 200 in 1138 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 129.118.58.15 |
|---|---|
| MX | 0 ttu-edu.mail.protection.outlook.com |
| NS | ns2-05.azure-dns.net ns3-05.azure-dns.org ns4-05.azure-dns.info ns1-05.azure-dns.com |
| TXT | AF15762DF8D6FE6227ADCED6A3E9A777 v=spf1 redirect=9dd2hzwe._spf._d.mim.ec fpqydlkv9wlc95nfjbh1py67wdly0q83 atlassian-sending-domain-verification=611bdab0-10c3-4474-a266-7b7de1d06fc8 lIYN5xenqPSHSY+lFvuiAE3AStAfhgkLa/8JKvnSSVRmFqO8prkkKCgrWla32m71wOHRU66K97xNKNMbHoBOSg== adobe-idp-site-verification=ff073f90c4da80c0ee92d3db1ba32bd333c6f3a341663d58d3d9e74d165d9ad5 atlassian-domain-verification=o1n0Izzs9DnNdLdIaaBwaqGbaaZwTToEtJzzJx3ah0n/LyZCeztU81xOSLaYJjF6 MS=ms30197301 oCb_lGUEbK82nIkr8UK5 google-site-verification=r2_kAC7-OFdQoNJrYTAZCB_a9G6H9zvDN00rBxokS2M pardot582863=5cca27502386ae37e7f8e77362e574c3ea47294dbaf7825c88616213a741fab4 |
| valid | yes |
|---|---|
| issuer | Internet2 |
| covers | ttu.edu |
| protocol | TLSv1.2 |
Domain is not signed with DNSSEC
| SPF | warning v=spf1 redirect=9dd2hzwe._spf._d.mim.ec |
|---|---|
| DMARC | warning policy none |
| DKIM | found: selector1, s1, s2 |
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 ttu.edu.
Reference: /llms.txt.
IPv6. Does ttu.edu work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch ttu.edu. 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