Skip to content
https://in.gov.br

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
73
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1790 ms total
FIX
2 redirect(s), 1790 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
Warning::
Redirect overhead: 1790 ms total
Got: 1790 ms
Info::
Cross-domain redirect detected

https://in.gov.br

817 ms · HTTP/1.1

301

https://www.gov.br/imprensanacional

736 ms · HTTP/1.1

301

https://www.gov.br/imprensanacional/pt-b...

237 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://in.gov.br301817 msHTTP/1.1
2https://www.gov.br/imprensanacional301736 msHTTP/1.1
3https://www.gov.br/imprensanacional/pt-b...200237 msHTTP/1.1

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

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

C
Crawlability
Action
robots.txt present, sitemap with 370 URLs
REVIEW
robots.txt present, sitemap with 370 URLs
Info::
robots.txt is present
Got: 25 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 370 entries
Info::
Sitemap index with 370 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

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 25 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 370 entries Valid XML Yes
Child Sitemaps:
C
HTTP Probe Timing
Action
Total 1506 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
667 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
209 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
416 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.51 s
Total Time Total request time from DNS lookup through full response.
1.51 s

Connection waterfall

DNS Lookup 667 ms TCP Connect 209 ms TLS Handshake 416 ms Server Processing 214 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
146 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 668 ms lookup
PASS
1 A records, 668 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 177.15.137.168
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: sharon.in.gov.br, luiza.in.gov.br
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
Warning::
DNS resolution is slow (668 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 668 ms
A177.15.137.168
AAAA—
CNAME—
NSsharon.in.gov.br, luiza.in.gov.br
MX
0 in-gov-br.mail.protection.outlook.com
TXT
SPF v=spf1 mx a:asmg.in.gov.br ip4:177.15.137.152/32 a mx include:spf.protection.out...
MS=ms72253514
MS=D08D2CC878C4CE8E3526D00AD45EA52CC25560E1
CAALookup not available with standard resolver
Resolved in 668 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

403https://www.in.gov.br/
200https://in.gov.br/

HTTP → HTTPS

302http://in.gov.br/ → https://www.in.gov.br/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
in.gov.br — 29 years, 10 months old, hosted on TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR
PASS
in.gov.br — 29 years, 10 months old, hosted on TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR
Info::
DNSSEC is enabled
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: TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR
Got: AS53237
Domain expiry

Unknown

SSL certificate

146 days

Issued by Sectigo Limited

Domain age

29 years, 10 months

Registered November 20, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR

ASN AS53237

177.15.137.168

Registrar

Registrar unknown

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created November 20, 1996 (29 years, 10 months ago)
Last Updated May 7, 2025
Name Servers sharon.in.gov.br, luiza.in.gov.br
DNSSEC Enabled
Registrant Imprensa Nacional/Presidência da República
Hosting
IP Address 177.15.137.168
ASN AS53237 (TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR)
Provider TELECOMUNICACOES BRASILEIRAS S. A. - TELEBRAS, BR
Data source: rdap (0.9s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback