Skip to content
https://infobae.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 107 ms total
REVIEW
2 redirect(s), 107 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect

https://infobae.com

28 ms · HTTP/1.1

301

https://infobae.com/america/

10 ms · HTTP/1.1

301

https://www.infobae.com/america/

69 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infobae.com30128 msHTTP/1.1AkamaiGHost
2https://infobae.com/america/30110 msHTTP/1.1AkamaiGHost
3https://www.infobae.com/america/20069 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

B
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

39
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.55.39.185, 23.55.39.162
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1413:5000:3::1736:7697, 2600:1413:5000:3::1736:7685
Info::
4 nameserver(s) configured
Got: ns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 10 ms
Got: 10 ms
A23.55.39.185, 23.55.39.162
AAAA2600:1413:5000:3::1736:7697, 2600:1413:5000:3::1736:7685
CNAME—
NSns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
facebook-domain-verification=9nx0qws1owa3hfjibhsrr2vdhgmpog
google-site-verification=_Yi38f0HraVtWKwud8037aVyOeqrIUQXilBacIqJQCo
atlassian-domain-verification=oPxVLUYLbWiUJK7Zt3dnGunJhv3iUKxSpEqQgCWnY096Oq9rgn...
SPF v=spf1 include:_spf.google.com include:_spf.createsend.com ~all
cisco-ci-domain-verification=fd7bebabfe8f6350badc1bc103f4e2678302e00f15e1734c7e6...
detectify-verification=9e0a697025628c6d25b50f40d34d3413
_github-challenge-infobaedev.www.infobae.com.=f35f471053
google-site-verification=Vg8r9d55DRa2BczKvGdMJSpWZ-h6VE_3IcS_F1wnJtU
dropbox-domain-verification=jm23otxrgs31
google-site-verification=th51xUhQvlz4itiPnhtAWuayW1Y99t0TCwDS8f1c8Ac
MS=ms57535613
CAALookup not available with standard resolver
Resolved in 10 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2600:1413:5000:3::1736:7697, 2600:1413:5000:3::1736:7685
Got: 2 ms connect
IPv6 Ready
AAAA Records 2600:1413:5000:3::1736:7697, 2600:1413:5000:3::1736:7685 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 100 URLs
PASS
robots.txt present, sitemap with 100 URLs
Info::
robots.txt is present
Got: 1360 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 100 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1360 B Sitemaps referenced 17 User-agents * Blocking No — crawling allowed
User-agent: *

Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap2/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap2/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap2/category/america/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap2/category/america/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap2/category/teleshow/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap2/category/teleshow/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap-index-static/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap/category/estados-unidos/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap/category/estados-unidos/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap/category/mexico/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap/category/mexico/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap/category/espana/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap/category/espana/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap/category/colombia/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap/category/colombia/
Sitemap: https://www.infobae.com/arc/outboundfeeds/news-sitemap/category/peru/
Sitemap: https://www.infobae.com/arc/outboundfeeds/sitemap/category/peru/

Disallow: /buscador
sitemap.xml 200 OK
Type URL Set URLs 100 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.infobae.com/
200https://infobae.com/

Preferred variant: non-www

HTTP → HTTPS

301http://infobae.com/ → https://infobae.com/america/

Consistent

A+
Domain Intelligence
infobae.com — via MarkMonitor Inc., 24 years, 4 months old
PASS
infobae.com — via MarkMonitor Inc., 24 years, 4 months old
Info::
Domain registered until Apr 5, 2027 (11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

262 days

April 5, 2027

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

24 years, 4 months

Registered April 5, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1417:76::6874:f3a3

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created April 5, 2002 (24 years, 4 months ago)
Expires April 5, 2027 (11 months)
Last Updated March 4, 2026
Name Servers ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 2600:1417:76::6874:f3a3
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 20 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
20 ms
Total Time Total request time from DNS lookup through full response.
20 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 10 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback