How is amzn.to?

Looks fine risk 0/100

Registered 17 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 79 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

79 ms · ends at www.amazon.com

HTTPS

31 d

left on a Let's Encrypt certificate

Age

17 years

registered 2010-03-12

Blocklists

listings across 5 lists

Everything we looked at

DNS records3 record types

A	67.199.248.12 67.199.248.13
NS	ns1.amzndns.co.uk ns1.amzndns.net ns1.amzndns.com ns2.amzndns.org ns1.amzndns.org ns2.amzndns.co.uk ns2.amzndns.com ns2.amzndns.net
TXT	v=spf1 -all

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	2010-03-12
expires	2028-03-12
last changed	2025-09-01
owner	Amazon Technologies, Inc.
nameservers	ns2.amzndns.org ns2.amzndns.net ns2.amzndns.com ns2.amzndns.co.uk
status	active client update prohibited client transfer prohibited client delete prohibited

registered 2010-03-12expires 2028-03-12

HTTPS certificate31 days left

valid	yes
issuer	Let's Encrypt
covers	amzn.to
protocol	TLSv1.3

issued 2026-08-29expires 2026-11-27

DNSSECinsecure

Domain is not signed with DNSSEC

. → to → amzn.to

Email authenticationfair

SPF	pass `v=spf1 -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 · 8 lookups

SURBL MultidomainURIBL MultidomainSpamCop67.199.248.12Barracuda67.199.248.12UCEPROTECT Level 167.199.248.12SpamCop67.199.248.13Barracuda67.199.248.13UCEPROTECT Level 167.199.248.13

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=amzn.to" \ -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=amzn.to"

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

Watch amzn.to. 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