Scanned sites / www.dioe.pr.gov.br / 2026-10-04-2102

www.dioe.pr.gov.br scan from 2026-10-04 21:02:48 UTC DR 39

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-04-2102

Scanned 2026-10-04 21:02:48 UTC, finished 2026-10-04 21:08:01 UTC

Site: https://www.dioe.pr.gov.br/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

50/ 100Needs work

On October 4, 2026 the Site Spider crawled 6 pages and 55 assets of www.dioe.pr.gov.br, starting from https://www.dioe.pr.gov.br/. It scored 50 out of 100, a result that needs work. 10 of 26 checks found something to fix, led by title tags (6), indexability (6), meta descriptions (6); 9 checks passed. Most of the points went to title tags (−10), indexability (−10), meta descriptions (−8). 7 checks found something the score does not count, listed as noted. 11 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium5 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
6
Assets fetched
55
Status
Completed
Checks with issues
10 of 26
CoverageComplete crawl

61 of 62 discovered URLs were fetched, 1 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript.

  • Title tags6 issues
    6 of 6 pages have title issues.
    −10 points
  • Meta descriptions6 issues
    6 of 6 pages have meta description issues.
    −8 points
  • Headings5 issues
    5 of 6 pages have heading issues.
    −5 points
  • Broken links1 issue
    2 internal links point at 1 broken URL.
    −3.3 points
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses1 issue
    3 URLs did not return a 2xx response. 1 of them is a page, 1 with an error status; the rest are assets or redirects.
    −1.7 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability6 issues
    6 of 6 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 8 image references have no alt attribute.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 55 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −0.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage3 issues
    No sitemap found. Tried: https://www.dioe.pr.gov.br/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link counts1 noted
    Internal link counts for 6 pages; 1 worth a look.
  • Thin content4 issues
    4 of 6 pages have fewer than 200 words.
    −5.3 points
  • Duplicate content2 issues
    1 group of pages with identical HTML.
    −2.7 points
  • URL format1 noted
    1 of 6 page URLs are harder to read, share or cache than they need to be.
  • Canonicals6 noted
    6 of 6 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 6 pages are open to search engines.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure2 noted
    2 of 6 pages could use the title, heading and snippet space better.
  • Image weight and alt length1 noted
    1 image over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 6 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookies1 noted
    1 cookie set by the site, 1 missing a protective flag; 9 response headers recorded across 61 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 6 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed Insights5 noted
    Mobile performance 70 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2343 sites, median 79%, average 78%

www.dioe.pr.gov.br scores 50%, higher than 2% of the 2343 scanned sites. See the full ranking.

0591170%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 84 sites80%: 108 sites81%: 105 sites82%: 117 sites83%: 99 sites84%: 108 sites85%: 88 sites86%: 70 sites87%: 73 sites88%: 59 sites89%: 65 sites90%: 36 sites91%: 46 sites92%: 39 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 sites50% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Written from an earlier version of the analysis (rules v5). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your website has several issues affecting SEO performance, including broken links, title and meta description problems, and missing sitemap. Fixing these will enhance search visibility.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO rankings.

    How: Update or remove internal links pointing to the broken URL: https://www.dioe.pr.gov.br/pdfs/parana/manual_particular.pdf.

    Checks: broken-links

  2. 2

    Add Sitemap

    Why: A sitemap helps search engines index your site effectively.

    How: Create a sitemap and place it at /sitemap.xml. Update robots.txt to reference it.

    Checks: sitemap-coverage

  3. 3

    Improve Title Tags

    Why: Title tags are crucial for SEO; they should be unique and relevant.

    How: Create unique titles for pages that currently share titles, especially for 4 pages sharing 'Diário Oficial / IOnews'.

    Checks: titles

  4. 4

    Write Meta Descriptions

    Why: Meta descriptions attract clicks from search results.

    How: Draft and add meta descriptions for all 6 pages to improve visibility.

    Checks: meta-descriptions

  5. 5

    Resolve Indexability Issues

    Why: Indexability warnings prevent proper page indexing by search engines.

    How: Add canonical and lang attributes to all 6 pages to resolve indexability warnings.

    Checks: indexability

  6. 6

    Add H1 Headings

    Why: H1 tags help search engines understand the main topic of your pages.

    How: Add a clear H1 tag to the 5 pages that currently lack it.

    Checks: headings

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The site has several missing security headers and outdated libraries, which can expose it to vulnerabilities. High-priority fixes include implementing HSTS and CSP, along with securing cookies. Updating vulnerable JavaScript libraries is also crucial.

  • 0 high
  • 5 medium
  • 3 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors may be intercepted on their first request for the site.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows unrestricted sources for scripts and styles, increasing XSS risk.

    Fix: Add the header: Content-Security-Policy: default-src 'self'; script-src 'self'

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Not using this header allows other sites to embed your pages in iframes, increasing clickjacking risks.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Missing Cookie Protection FlagsMedium

    Why it matters: Cookies lacking protections can be accessed by unauthorized scripts, leading to session hijacking.

    Fix: Set cookie flags: Secure; HttpOnly; SameSite=Strict

    Evidence: Cookie flags

  5. 5

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated libraries may be exploited if vulnerabilities are active in your specific use.

    Fix: Upgrade jQuery to at least 3.5.0 and Bootstrap to at least 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly interpret files, leading to potential script injection.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer-PolicyLow

    Why it matters: Lack of a referrer policy exposes sensitive URL information when users navigate away.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  8. 8

    Software Version DisclosureLow

    Why it matters: Revealing server version info enables attackers to exploit known vulnerabilities.

    Fix: Hide server version by configuring Apache to remove or modify the server banner.

    Evidence: Software version disclosure

  9. 9

    Missing Permissions PolicyInfo

    Why it matters: A Permissions-Policy header can restrict features that could be abused by malicious scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(), microphone=(), camera=()

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.dioe.pr.gov.br/ → no strict-transport-security
    • https://www.dioe.pr.gov.br/cadastro → no strict-transport-security
    • https://www.dioe.pr.gov.br/listagem → no strict-transport-security
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no strict-transport-security
    • https://www.dioe.pr.gov.br/login → no strict-transport-security
    • https://www.dioe.pr.gov.br/cadastro/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 6 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://www.dioe.pr.gov.br/ → no content-security-policy
    • https://www.dioe.pr.gov.br/cadastro → no content-security-policy
    • https://www.dioe.pr.gov.br/listagem → no content-security-policy
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no content-security-policy
    • https://www.dioe.pr.gov.br/login → no content-security-policy
    • https://www.dioe.pr.gov.br/cadastro/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://www.dioe.pr.gov.br/ → no x-frame-options
    • https://www.dioe.pr.gov.br/cadastro → no x-frame-options
    • https://www.dioe.pr.gov.br/listagem → no x-frame-options
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no x-frame-options
    • https://www.dioe.pr.gov.br/login → no x-frame-options
    • https://www.dioe.pr.gov.br/cadastro/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://www.dioe.pr.gov.br/ → no x-content-type-options
    • https://www.dioe.pr.gov.br/cadastro → no x-content-type-options
    • https://www.dioe.pr.gov.br/listagem → no x-content-type-options
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no x-content-type-options
    • https://www.dioe.pr.gov.br/login → no x-content-type-options
    • https://www.dioe.pr.gov.br/cadastro/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://www.dioe.pr.gov.br/ → no referrer-policy
    • https://www.dioe.pr.gov.br/cadastro → no referrer-policy
    • https://www.dioe.pr.gov.br/listagem → no referrer-policy
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no referrer-policy
    • https://www.dioe.pr.gov.br/login → no referrer-policy
    • https://www.dioe.pr.gov.br/cadastro/ → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://www.dioe.pr.gov.br/ → no permissions-policy
    • https://www.dioe.pr.gov.br/cadastro → no permissions-policy
    • https://www.dioe.pr.gov.br/listagem → no permissions-policy
    • https://www.dioe.pr.gov.br/usuarios/recupera_senha → no permissions-policy
    • https://www.dioe.pr.gov.br/login → no permissions-policy
    • https://www.dioe.pr.gov.br/cadastro/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Apache/2.4.52 (Ubuntu) (61 responses)
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • CAKEPHP (set by https://www.dioe.pr.gov.br/) lacks Secure, SameSite
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 3.3.1, Bootstrap 3.3.4. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.3.1 in https://www.dioe.pr.gov.br/js/jquery.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • Bootstrap 3.3.4 in https://www.dioe.pr.gov.br/js/bootstrap.min.js: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
  • NoteThird-party scripts

    Scripts run from 2 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • www.googletagmanager.com (6 script tags)
    • www.google.com (1 script tag)
5 checks passed, 1 not applicable
  • OKHTTPS

    All 6 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    9 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near www.dioe.pr.gov.br

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.dioe.pr.gov.br from its pages as published, the way a search engine does. It shows summary figures only.

Own www.dioe.pr.gov.br?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.dioe.pr.gov.br. Removal needs no account and no proof of purchase.