Skip to content
https://abril.com.br

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
A
DNS Records
1 A records, 209 ms lookup
PASS
1 A records, 209 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.160
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a3.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
Warning::
DNS resolution is slow (209 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 209 ms
A192.0.66.160
AAAA
CNAME
NSns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a3.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbm1vUEpmdRPJeR75mi9H7EcXoItIBLCC...
betaabril.wordpress.com.
facebook-domain-verification=a0u9vfnz8julo36kk633p8oubb11w9
Sendinblue-code:ae39671320aad04ffb3ff66ae2ef687f
pOElGlMtpZhP7mWHjoDncidwzAmyJ7r09Fp8SSGiy1k/40A63bTlFrR+YdYaIhrWKk8zoNjPHPK6FKXB...
google-site-verification=qCp0_xH1W53T5bK4pUKtNDNCgj9tJu3P-Bg3bNGcE3A
google-site-verification=2eRijxsvfL3Ny2afBf_jgRKCtkQT7Zq-JbzdS6TZ1zg
SPF v=spf1 include:_spf.google.com ip4:177.36.226.144 ip4:177.36.226.191 include:spf...
adobe-idp-site-verification=3feee384-f42a-4c47-9ca4-4a4cd6a78a29
google-site-verification=SRDCYf9jbz11Gx3sCg1tzitySdcS5K20Avk-jWU2cQw
MS=ms63008408
CAALookup not available with standard resolver
Resolved in 209 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 75 ms total
PASS
1 redirect(s), 75 ms total
Info::
Single redirect
Got: https://abril.com.br → https://assine.abril.com.br/?redirect=abrilcom (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://abril.com.br
Info::
Cross-domain redirect detected

https://abril.com.br

6 ms · HTTP/1.1

302

https://assine.abril.com.br/?redirect=ab...

69 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://abril.com.br3026 msHTTP/1.1nginx
2https://assine.abril.com.br/?redirect=ab...20069 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 282 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 282 B Sitemaps referenced 3 User-agents *, googlebot Blocking No — crawling allowed
Sitemap: https://abril.com.br/news-sitemap.xml

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://abril.com.br/sitemap-webstories.xml

# Sitemap archive
Sitemap: https://abril.com.br/sitemap.xml



User-agent: googlebot
Disallow: /*/pdf_reader/*/


sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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

302https://www.abril.com.br/
200https://abril.com.br/

Preferred variant: non-www

HTTP → HTTPS

301http://abril.com.br/ https://abril.com.br/

Consistent

A+
Domain Intelligence
abril.com.br — 31 years, 4 months old, hosted on WordPress.com (Automattic)
PASS
abril.com.br — 31 years, 4 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jan 1, 2028 (1 years, 8 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.
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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

538 days

January 1, 2028

SSL certificate

290 days

Issued by DigiCert Inc

Domain age

31 years, 4 months

Registered May 16, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.160

Registrar

Registrar unknown

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
Created May 16, 1995 (31 years, 4 months ago)
Expires January 1, 2028 (1 years, 8 months)
Last Updated October 2, 2024
Name Servers ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
DNSSEC Not enabled
Registrant ABRIL COMUNICACOES S.A.
Hosting
IP Address 192.0.66.160
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (1.0s)

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 325 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 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.
325 ms
Total Time Total request time from DNS lookup through full response.
325 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 298 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