How is infobae.com?
Looks fine
risk 0/100
Registered 25 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 573 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
573 ms · ends at www.infobae.com
HTTPS
59 d
left on a Let's Encrypt certificate
Age
25 years
registered 2002-04-05
Blocklists
0
listings across 5 lists
Everything we looked at
DNS records5 record types
| A | 23.64.114.219 23.64.114.205 |
|---|---|
| AAAA | 2600:1407:3c00:1868::17dc:9012 2600:1407:3c00:1868::17dc:900b |
| MX | 1 aspmx.l.google.com 10 aspmx3.googlemail.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com |
| NS | ns-cloud-d4.googledomains.com ns-cloud-d1.googledomains.com ns-cloud-d3.googledomains.com ns-cloud-d2.googledomains.com |
| TXT | cisco-ci-domain-verification=fd7bebabfe8f6350badc1bc103f4e2678302e00f15e1734c7e6ef0d9ae77956 detectify-verification=9e0a697025628c6d25b50f40d34d3413 facebook-domain-verification=9nx0qws1owa3hfjibhsrr2vdhgmpog dropbox-domain-verification=jm23otxrgs31 MS=ms57535613 google-site-verification=th51xUhQvlz4itiPnhtAWuayW1Y99t0TCwDS8f1c8Ac _github-challenge-infobaedev.www.infobae.com.=f35f471053 v=spf1 include:_spf.google.com include:_spf.createsend.com ~all google-site-verification=_Yi38f0HraVtWKwud8037aVyOeqrIUQXilBacIqJQCo atlassian-domain-verification=oPxVLUYLbWiUJK7Zt3dnGunJhv3iUKxSpEqQgCWnY096Oq9rgnZLBEvYFGVOJtzm google-site-verification=Vg8r9d55DRa2BczKvGdMJSpWZ-h6VE_3IcS_F1wnJtU |
RegistrationMarkMonitor Inc.
| registrar | MarkMonitor Inc. |
|---|---|
| registered | 2002-04-05 |
| expires | 2027-04-05 |
| last changed | 2026-03-04 |
| owner | REDACTED FOR PRIVACY |
| nameservers | ns-cloud-d1.googledomains.com ns-cloud-d2.googledomains.com ns-cloud-d3.googledomains.com ns-cloud-d4.googledomains.com |
| status | client delete prohibited client transfer prohibited client update prohibited server delete prohibited server transfer prohibited server update prohibited |
registered 2002-04-05expires 2027-04-05
HTTPS certificate59 days left
| valid | yes |
|---|---|
| issuer | Let's Encrypt |
| covers | api-infobae-infobae-prod.cdn.arcpublishing.com, api-infobae-infobae-sandbox.cdn.arcpublishing.com, api-infobae-prod.cdn.arcpublishing.com, api-infobae-sandbox.cdn.arcpublishing.com, apis.infobae.com, cdn-app.infobae.arcpublishing.com, cdn-staging.infobae.arcpublishing.com, cdn-www.infobae.arcpublishing.com, infobae-config-prod.api.cdn.arcpublishing.com, infobae-config-sandbox.api.cdn.arcpublishing.com, infobae.com, infobae.web.arc-cdn.net |
| protocol | TLSv1.3 |
issued 2026-09-28expires 2026-12-27
DNSSECinsecure
Domain is not signed with DNSSEC
. → com → infobae.com
Email authenticationexcellent
| SPF | pass v=spf1 include:_spf.google.com include:_spf.createsend.com ~all |
|---|---|
| DMARC | pass policy reject |
| DKIM | found: google, s1, s2 |
Whether mail claiming to be from this domain can be checked as genuine.
Security scoregrade B · 160/205
Basic Security10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security30/45missing: CAA Records, DKIM Presence
Advanced Security25/25
Domain Reputation50/50
Threat Detection45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop23.221.227.34Barracuda23.221.227.34UCEPROTECT Level 123.221.227.34SpamCop23.221.227.13Barracuda23.221.227.13UCEPROTECT Level 123.221.227.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=infobae.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=infobae.com"
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on infobae.com.
Reference: /llms.txt.
Watch infobae.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