HOW.IS
?

How is 33across.com?

Looks fine risk 0/100

Registered 19 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 81 ms.

Why

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

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

How 33across.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
403
81 ms
HTTPS
30 d
left on a Let's Encrypt certificate
Age
19 years
registered 2007-09-29
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A151.101.194.159
MX10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 alt3.aspmx.l.google.com
30 alt4.aspmx.l.google.com
20 alt1.aspmx.l.google.com
NSns51.constellix.net
ns41.constellix.net
ns21.constellix.com
ns31.constellix.com
ns11.constellix.com
ns61.constellix.net
TXTgoogle-site-verification=AqYTvL5bFYGZvakCh8MuHVA1w2ejHunmwwSMuQ8l_7k
ca3-31f5a429c517415d92c2cabb300d3b7a
v=spf1 ip4:72.28.123.96/27 include:_spf.google.com include:441909.spf08.hubspotemail.net ~all
apple-domain-verification=5KYMuI9mIS9XRh8S
CAA{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'pki.goog', 'critical': 0}
RegistrationGoDaddy.com, LLC
registrarGoDaddy.com, LLC
registered2007-09-29
expires2028-09-29
last changed2026-09-30
nameserversns11.constellix.com
ns21.constellix.com
ns31.constellix.com
ns41.constellix.net
ns51.constellix.net
ns61.constellix.net
statusclient delete prohibited
client renew prohibited
client transfer prohibited
client update prohibited
registered 2007-09-29expires 2028-09-29
HTTPS certificate30 days left
validyes
issuerLet's Encrypt
covers33across.com
protocolTLSv1.3
issued 2026-08-29expires 2026-11-27
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → 33across.com
Email authenticationgood
SPFpass v=spf1 ip4:72.28.123.96/27 include:_spf.google.com include:441909.spf08.hubspotemail.net ~all
DMARCwarning policy none
DKIMfound: google, s1, s2

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

Security scoregrade B · 173/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
38/45missing: DMARC Record, 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 MultidomainSpamCop151.101.194.159Barracuda151.101.194.159UCEPROTECT Level 1151.101.194.159

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=33across.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=33across.com"

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

Watch 33across.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