How is adobe.io?

Looks fine risk 0/100

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

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

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

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

90 ms · ends at developer.adobe.com

HTTPS

34 d

left on a DigiCert Inc certificate

Age

15 years

registered 2012-03-12

Blocklists

listings across 5 lists

Everything we looked at

DNS records3 record types

A	54.227.187.23 52.202.204.11 52.5.13.197 23.22.254.206
NS	ns-1159.awsdns-16.org ns-1882.awsdns-43.co.uk ns-67.awsdns-08.com ns-1001.awsdns-61.net
TXT	_globalsign-domain-verification=fglY8fW9FHwF88bTrkylG5-G165KrJe3yCIjKnAR9J google-site-verification=Fi3ns_oehupSf-VeeFG1WotomwJppBwMcBy8-AQa1Yg b2c6caadfdbe4133b3f19e912154f522 v=spf1 include:amazonses.com -all 63148376f85b40b0b02b94ffaf3ad2c6 2g6pqbqfz4qzmg4g3x5wf72zrtb1t0s6 google-site-verification=suOk_OKGZgKKpn7EIFIN2dCQiru4D00Fr2MEbBPT5XE tn2rh7ty1t1870l38gl2t8x0wp413n6y google-site-verification=rhilqPhSevdWD-lQyxNTPSmEGQPrWjqeV2nW9yAD9Co x1xcnfnh0185r7c1fnbl0ccyn7yl5lqd by1c76jcvvtn0m7kcblv8c8xzk82n4kv

RegistrationNom-iq Ltd. dba COM LAUDE

registrar	Nom-iq Ltd. dba COM LAUDE
registered	2012-03-12
expires	2027-03-12
last changed	2026-08-12
owner	Adobe Inc.
nameservers	ns-1001.awsdns-61.net ns-1159.awsdns-16.org ns-67.awsdns-08.com ns-1882.awsdns-43.co.uk
status	client delete prohibited client transfer prohibited client update prohibited

registered 2012-03-12expires 2027-03-12

HTTPS certificate34 days left

valid	yes
issuer	DigiCert Inc
covers	adobe.io, .private.adobe.io, oobesaas.adobe.com, .publish.adobe.io, .adobe.io, .lab.publish.adobe.io, adobesc.com, .licenses.adobe.com, .adobesc.com, .adobecontent.io, .lab.digitalpublishing.adobe.io, licenses.adobe.com
protocol	TLSv1.3

issued 2026-05-14expires 2026-11-28

DNSSECinsecure

Domain is not signed with DNSSEC

. → io → adobe.io

Email authenticationfair

SPF	pass `v=spf1 include:amazonses.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.

Security scoregrade B · 155/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

10/25missing: Mail Server Configuration, IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 14 lookups

SURBL MultidomainURIBL MultidomainSpamCop18.207.85.246Barracuda18.207.85.246UCEPROTECT Level 118.207.85.246SpamCop107.22.247.231Barracuda107.22.247.231UCEPROTECT Level 1107.22.247.231SpamCop54.144.73.197Barracuda54.144.73.197UCEPROTECT Level 154.144.73.197SpamCop34.193.227.236Barracuda34.193.227.236UCEPROTECT Level 134.193.227.236

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=adobe.io" \ -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=adobe.io"

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

Watch adobe.io. 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