HOW.IS
?

How is twitter.com?

Looks fine risk 0/100

Registered 27 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 177 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How twitter.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
177 ms · ends at x.com
HTTPS
63 d
left on a Let's Encrypt certificate
Age
27 years
registered 2000-01-21
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records4 record types
A172.66.0.227
MX1 aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
NSa.r06.twtrdns.net
a.u06.twtrdns.net
b.r06.twtrdns.net
b.u06.twtrdns.net
c.r06.twtrdns.net
c.u06.twtrdns.net
d.r06.twtrdns.net
d.u06.twtrdns.net
TXT0a8c0fc6-bfa5-4ea7-b09b-87f2989022d6
MS=BEE202D20C326867290BDEFA2DDDF4594B5D6860
adobe-idp-site-verification=a2ff8fc40c434d1d6f02f68b0b1a683e400572ab8c1f2c180c71c3d985b9270a
apple-domain-verification=zd1iHoEO9LILEQIq
atlassian-domain-verification=j6u0o1PTkobCXC84uEF/sWpIPtaZURBVYqKzmTvT8wugLcHT1vvrzzA63iP1qSLN
bj6sbt5xqs9hw9jrfvz7hplrg0l680sb
canva-site-verification=lMnZ3wMh7c1uqZqa-cxZTg
google-site-verification=600dQ0pZYsH2xOFt4hYmf5f5NpjCbWE_qk5Y04dErYM
google-site-verification=F2uUiLUsD6kQlpUVQzxUM3PHa0uPo5GBS84SCG8QwXI
google-site-verification=P9-NRZ0gaRKRGNDOXOjct5XETPtr3P9D-XA8HnlbAy4
google-site-verification=TNhAkfLUeIbzzzSgPNxS5aEkKMf3aUcpPmCK1_kmIvU
google-site-verification=h6dJIv0HXjLOkGAotLAWEzvoi9SxqP4vjpx98vrCvvQ
google-site-verification=q1ghWjGLX9Ba-Gy_B4n_pAgC_mQYzWmQpOD8CMWl_Hw
linear-domain-verification=t5iq7e7nbw5w
loom-site-verification=638c6bc173b9458997f64d305bf42499
miro-verification=6e1ca9ad6d0c2cd2e4186141265f23ed618cfe37
mixpanel-domain-verify=164dda91-31f4-41e8-a816-0f59b38fea30
notion-domain-verification=uKi5TAGxlhWMHG9uHKHkDY3cVc6zraAE1I44bILENlB
slack-domain-verification=9oO8P4Glf4252QJDOg4rHGs6KlSkBuI5ZVmWRO8d
stripe-verification=46F7B88485621DC18923B43D12E90E6CDBCE232F2FEBCF084E6EFA91F6BA707D
traction-guest=6882b04e-4188-4ff9-8bb4-bff5a3d358e6
traction-guest=a4d0248d-fe01-4222-8fcc-33f68323e667
v=spf1 ip4:199.16.156.0/22 ip4:199.59.148.0/22 ip4:8.25.194.0/23 ip4:8.25.196.0/23 ip4:204.92.114.203 ip4:204.92.114.204/31 include:_spf.google.com include:_thirdparty.twitter.com -all
wrike-verification=MjU4MTA5MjoyN2UzNDc1MjU3MDZiZTY4NjBiNzliNDQ2OTUwNWY3NmM5NDgyMTBlYzFkNTcwYTE2YWNmZDdkNTY2ZmE4Yzlh
RegistrationCSC Corporate Domains, Inc.
registrarCSC Corporate Domains, Inc.
registered2000-01-21
expires2027-01-21
last changed2026-01-17
ownerTwitter, Inc.
nameserversa.r06.twtrdns.net
a.u06.twtrdns.net
b.r06.twtrdns.net
b.u06.twtrdns.net
c.r06.twtrdns.net
c.u06.twtrdns.net
d.r06.twtrdns.net
d.u06.twtrdns.net
statusclient transfer prohibited
server delete prohibited
server transfer prohibited
server update prohibited
registered 2000-01-21expires 2027-01-21
HTTPS certificate63 days left
validyes
issuerLet's Encrypt
covers*.twitter.com, cdn.syndication.twitter.com, twitter.com
protocolTLSv1.3
issued 2026-09-28expires 2026-12-27
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → twitter.com
Email authenticationexcellent
SPFpass v=spf1 ip4:199.16.156.0/22 ip4:199.59.148.0/22 ip4:8.25.194.0/23 ip4:8.25.196.0/23 ip4:204.92.114.203 ip4:204.92.114.204/31 include:_spf.google.com include:_thirdparty.twitter.com -all
DMARCpass policy reject
DKIMfound: google, dkim

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade B · 155/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
20/25missing: IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop172.66.0.227Barracuda172.66.0.227UCEPROTECT Level 1172.66.0.227

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

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.

curl "https://how.is/v1/domain/trust?domain=twitter.com" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=twitter.com"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on twitter.com. Reference: /llms.txt.

Watch twitter.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