How is smadex.com?

Looks fine risk 0/100

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

356 ms

HTTPS

153 d

left on a Amazon certificate

Age

15 years

registered 2012-01-03

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	3.170.19.113 3.170.19.112 3.170.19.100 3.170.19.84
MX	1 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
NS	ns-113.awsdns-14.com ns-1524.awsdns-62.org ns-1631.awsdns-11.co.uk ns-581.awsdns-08.net
TXT	MS=ms35543082 anthropic-domain-verification-an1rwp=iBVROYwTG8bpQlbWGTwmoCvWu apple-domain-verification=maQSz0FFIUxfmd3i brevo-code:f79e57f5a0a50773725ada0e6c1b8fef google-site-verification=H_OYHbQ_q6dk1-qdphwz8Yj5NfFg9vx3oWC2fKuj7QQ google-site-verification=Y7MMpWICnPXA923nx3lt_R1Zur2JmHKZB4nC9s0ofWs google-site-verification=tIKLlGryzUqtbt01Xu_LmFE3WTNVBFF_PBFkG7bMr88 google-site-verification=xw9HKRreWIWnz24si1IgeHFBP2cP1ON6Kx0Hr48VdP8 knowbe4-site-verification=b1e4265253be2f0139222d439a22dadf notion-domain-verification=iJscteqlLG325yIPctvt8iQItxCU6gjEo55GlzHvBP4 sending_domain878332=69053dcd667f7d6179778e9145c7829e3074b81a86a036fbfc99ff49d800fa9f spf2.0/pra include:_spf.google.com include:amazonses.com ~all v=spf1 include:_spf.google.com include:amazonses.com include:_spf.salesforce.com include:_spf.ultipro.com ~all yp4otogoe7

RegistrationAmazon Registrar, Inc.

registrar	Amazon Registrar, Inc.
registered	2012-01-03
expires	2027-01-03
last changed	2026-05-14
owner	c/o whoisproxy.com
nameservers	ns-113.awsdns-14.com ns-1524.awsdns-62.org ns-1631.awsdns-11.co.uk ns-581.awsdns-08.net
status	client transfer prohibited

registered 2012-01-03expires 2027-01-03

HTTPS certificate153 days left

valid	yes
issuer	Amazon
covers	smadex.com, smadex.ai, .smadex.es, smadex.es, .smadex.com, *.smadex.ai
protocol	TLSv1.3

issued 2026-09-17expires 2027-04-02

DNSSECinsecure

Domain is not signed with DNSSEC

. → com → smadex.com

Email authenticationexcellent

SPF	pass `v=spf1 include:_spf.google.com include:amazonses.com include:_spf.salesforce.com include:_spf.ultipro.com ~all`
DMARC	pass policy quarantine
DKIM	found: google

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

Security scoregrade B · 165/205

Basic Security

20/40missing: DNSSEC Enabled

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 · 14 lookups

SURBL MultidomainURIBL MultidomainSpamCop3.170.19.112Barracuda3.170.19.112UCEPROTECT Level 13.170.19.112SpamCop3.170.19.100Barracuda3.170.19.100UCEPROTECT Level 13.170.19.100SpamCop3.170.19.84Barracuda3.170.19.84UCEPROTECT Level 13.170.19.84SpamCop3.170.19.113Barracuda3.170.19.113UCEPROTECT Level 13.170.19.113

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

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

IPv6. Does smadex.com work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

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