HOW.IS
?

How is sapo.pt?

Not sure yet risk 10/100

On no blocklists we checked, valid HTTPS, the site answered 200 in 496 ms.

Why

02050100
finecarefulhigh risk
  • +10The registry did not report a usable creation date.
  • ·Could not check domain age; retry before trusting this domain.

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

How sapo.pt looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
496 ms
HTTPS
9 d
left on a DigiCert Inc certificate
Age
?
creation date not reported
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records5 record types
A213.13.145.114
MX5 mx.sapo.pt
NSns2.sapo.pt
dns01.sapo.pt
dns02.sapo.pt
ns.sapo.pt
TXTf287y09s2zsj9hptkxzs5lzgrvwg8j27
mtc=ODU0ODBlNzEtODFjNC00ZWE1LTk2NmMtOTM2MGQyZDVlNmY0
google-site-verification=seX0gQu5Yl29CzyK9E5_5y6npSkuTbTDmPHF4amEz2k
_globalsign-domain-verification=V7TYz76TZVst185h-018Crj3WPkm7xwIw5ZIrYXG41
v=spf1 include:_spf.sapo.pt -all
CAA{'type': 'CAA', 'issue': 'letsencrypt.org', 'critical': 0}
{'type': 'CAA', 'issue': 'digicert.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'digicert.com'}
{'type': 'CAA', 'issue': 'godaddy.com', 'critical': 0}
{'type': 'CAA', 'iodef': 'mailto:opers@co.sapo.pt', 'critical': 0}
{'type': 'CAA', 'issue': 'amazon.com', 'critical': 0}
{'type': 'CAA', 'issue': 'amazontrust.com', 'critical': 0}
{'type': 'CAA', 'issue': 'amazonaws.com', 'critical': 0}
{'type': 'CAA', 'issue': 'awstrust.com', 'critical': 0}
{'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'issuewild': 'globalsign.com'}
{'type': 'CAA', 'critical': 0, 'issuewild': 'letsencrypt.org'}
{'type': 'CAA', 'issue': 'sectigo.com', 'critical': 0}
Registrationregistrar not reported
expires2027-02-11
nameserversns2.sapo.pt | ipv4: 212.55.154.194 and ipv6: dns01.sapo.pt | ipv4: 213.13.28.116 and ipv6: 2001:8a0:2106:4:213:13:28:116 dns02.sapo.pt | ipv4: 213.13.30.116 and ipv6: 2001:8a0:2206:4:213:13:30:116 ns.sapo.pt | ipv4: 212.55.154.202 and ipv6:
statusRegistered
HTTPS certificate9 days left
validyes
issuerDigiCert Inc
covers*.sapo.pt, sapo.pt
protocolTLSv1.3
issued 2025-10-21expires 2026-11-07
DNSSECinsecure

Domain is not signed with DNSSEC

. → pt → sapo.pt
Email authenticationgood
SPFpass v=spf1 include:_spf.sapo.pt -all
DMARCpass policy quarantine
DKIMnone of 1 common selectors

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

Security scoregrade B · 165/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
45/45missing: DKIM Presence
Advanced Security
15/25missing: Mail Server Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop213.13.145.114Barracuda213.13.145.114UCEPROTECT Level 1213.13.145.114

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=sapo.pt" \ -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=sapo.pt"

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

Watch sapo.pt. 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