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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 3678 ms total
FIX
2 redirect(s), 3678 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: 3678 ms total
Got: 3678 ms

https://sp.gov.br

568 ms · HTTP/1.1

301

https://www.sp.gov.br/

901 ms · HTTP/1.1

301

https://www.sp.gov.br/sp

2208 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sp.gov.br301568 msHTTP/1.1nginx
2https://www.sp.gov.br/301901 msHTTP/1.1nginx
3https://www.sp.gov.br/sp2002208 msHTTP/1.1nginx

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

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

Connection waterfall

DNS Lookup 175 ms TCP Connect 83 ms TLS Handshake 87 ms Server Processing 533 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
297 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

297
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
B
CDN & Delivery
Incapsula
REVIEW
Incapsula
Info::
Site is served via Incapsula CDN
Got: x-iinfo: 49-5285642-5285662 NNNN CT(147 152 0) RT(1776806726693 87) q(0 0 3 0) r(4 4) U11
CDN Detected: Incapsula
Provider Incapsula Evidence x-iinfo: 49-5285642-5285662 NNNN CT(147 152 0) RT(1776806726693 87) q(0 0 3 0) r(4 4) U11
A+
DNS Records
1 A records, 196 ms lookup
PASS
1 A records, 196 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 45.223.122.140
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: dns1e.sp.gov.br, dns4e.sp.gov.br, dns2e.sp.gov.br, dns3e.sp.gov.br, dns5e.sp.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
Info::
DNS resolution time: 196 ms
Got: 196 ms
A45.223.122.140
AAAA
CNAME
NSdns1e.sp.gov.br, dns4e.sp.gov.br, dns2e.sp.gov.br, dns3e.sp.gov.br, dns5e.sp.gov.br
MX
10 sp-gov-br.mail.protection.outlook.com
TXT
google-site-verification=LqtNDh4bDgMh5NtcykBkqksC6Oay4XOMceZpJI6_clw
_qwjgs5vhk041z7urutshd2s8ghpyx6u
MS=ms62971617
_6mgtepqm3la7y8cummstybim4h58hw5
10NGZRXWI9VIHD0GE51BMK6HMN4KG7NA6G2X2C53
_globalsign-domain-verification=V4qyMqcUN2zlmhsfwj8dPBppLSKwGrQSt_e0DeV1Fk
6N5OPNO8OEWQVXGCC0HMJ8HU3I1A3WGS8Y9IH94P
4tSeIqHAFTbAS3C++QyS0X8KHbQOxSF7Vk1Y+lVW9bo=
dtm-domain-verification=zn1sk_pElaZH-5baJsQNnwZdxR7ZTkyokCEpdVIXhkU
yahoo-verification-key=iasl4TPlDSJLpXurPXN8DbUuLJP2cdSFO876CjnwkG8=
SPF v=spf1 include:correio-spfsmtp.prodesp.sp.gov.br include:spf.protection.outlook....
M2P1LD20T2ZXNCN0C1O4O5LFWHN748024NZEC603
CAALookup not available with standard resolver
Resolved in 196 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 9499 URLs
PASS
robots.txt present, sitemap with 9499 URLs
Info::
robots.txt is present
Got: 63 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9499 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 63 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
 
Sitemap: https://sp.gov.br/sitemap.xml
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.sp.gov.br/
200https://sp.gov.br/

Preferred variant: non-www

HTTP → HTTPS

301http://sp.gov.br/ https://www.sp.gov.br/

Consistent

A+
Domain Intelligence
sp.gov.br — 31 years, 2 months old, hosted on INCAPSULA - Incapsula Inc, US
PASS
sp.gov.br — 31 years, 2 months old, hosted on INCAPSULA - Incapsula Inc, US
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: INCAPSULA - Incapsula Inc, US
Got: AS19551
Domain expiry

Unknown

SSL certificate

297 days

Issued by GlobalSign nv-sa

Domain age

31 years, 2 months

Registered July 6, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

INCAPSULA - Incapsula Inc, US

ASN AS19551

45.223.122.140

Registrar

Registrar unknown

Unlocked 5 NS records
Expiry timeline
Today
+1 year
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 July 6, 1995 (31 years, 2 months ago)
Last Updated August 22, 2024
Name Servers dns1e.sp.gov.br, dns3e.sp.gov.br, dns2e.sp.gov.br, dns4e.sp.gov.br, dns5e.sp.gov.br
DNSSEC Not enabled
Registrant Cia Proc. de Dados do Estado de S Paulo - Prodesp
Hosting
IP Address 45.223.122.140
ASN AS19551 (INCAPSULA - Incapsula Inc, US)
Provider INCAPSULA - Incapsula Inc, US
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

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

Send Feedback