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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.ig.com.br/
200https://ig.com.br/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ig.com.br/ http://www.ig.com.br/

HTTP version does not redirect to HTTPS

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.

B
Redirect Chain
2 redirect(s), 111 ms total
REVIEW
2 redirect(s), 111 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://ig.com.br to https://www.ig.com.br/

https://ig.com.br

29 ms · HTTP/1.1

301

http://www.ig.com.br/

23 ms · HTTP/1.1

301

https://www.ig.com.br/

59 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ig.com.br30129 msHTTP/1.1nginx/1.18.0 (Ubuntu)
2http://www.ig.com.br/30123 msHTTP/1.1cloudflare
3https://www.ig.com.br/20059 msHTTP/1.1cloudflare

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

Redirect directly from https://ig.com.br to https://www.ig.com.br/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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
48 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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, 5 ms lookup
PASS
1 A records, 5 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.198.170.253
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-1118.awsdns-11.org, ns-1766.awsdns-28.co.uk, ns-485.awsdns-60.com, ns-798.awsdns-35.net
Info::
1 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: 5 ms
Got: 5 ms
A54.198.170.253
AAAA
CNAME
NSns-1118.awsdns-11.org, ns-1766.awsdns-28.co.uk, ns-485.awsdns-60.com, ns-798.awsdns-35.net
MX
1 mx-ha.skymail.net.br
TXT
clicksign-domain-verification=XJboDnoTsHVIam6hoSkZZrqrlp0lstIjCAhrXs+D030=
facebook-domain-verification=bp7hn5kcbtfmzruv02fal61fk3vk49
google-site-verification=289AV2EJTdecRJjQr9w3tiL_oPCLuQBr65aFHRQoC3U
google-site-verification=BiAhckwo5_ZlVJLy-5Np9ASq_CdUGBmp1Ngkgcwwr6A
google-site-verification=DHISx-Ex9KiXgtW6P7cc3AY-LfGDFcPF36JiRH1W2Eg
ip4:191.252.30.0/25 ip4:191.252.7.128/25 ip4:191.252.30.128/25 ip4:191.252.14.0/...
mandrill_verify.hK7vG4KaNFp6hppMO0ZhQw
SPF v=spf1 a mx ip4:177.153.28.0/24 ip4:201.76.63.0/24 ip4:177.153.24.32/27 ip4:177....
CAALookup not available with standard resolver
Resolved in 5 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.

A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 1738 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1738 B Sitemaps referenced 0 User-agents CloudflareBrowserRenderingCrawler, meta-externalagent, *, Amazonbot, Applebot-Extended, Google-Extended, GPTBot, Bytespider, CCBot, ClaudeBot Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


A+
Domain Intelligence
ig.com.br — 28 years, 4 months old, hosted on AWS
PASS
ig.com.br — 28 years, 4 months old, hosted on AWS
Info::
Domain registered until May 5, 2027 (1 years 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: AWS
Got: AS14618
Domain expiry

297 days

May 5, 2027

SSL certificate

48 days

Issued by Let's Encrypt

Domain age

28 years, 4 months

Registered May 5, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.198.170.253

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 5, 1998 (28 years, 4 months ago)
Expires May 5, 2027 (1 years)
Last Updated April 14, 2025
Name Servers ns-1766.awsdns-28.co.uk, ns-1118.awsdns-11.org, ns-485.awsdns-60.com, ns-798.awsdns-35.net
DNSSEC Not enabled
Registrant Holy Rock Desenvolvimento de Negócios Ltda.
Hosting
IP Address 54.198.170.253
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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 91 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
67 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
91 ms
Total Time Total request time from DNS lookup through full response.
92 ms

Connection waterfall

DNS Lookup 67 ms TCP Connect 7 ms TLS Handshake 9 ms Server Processing 8 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