The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://verifieddr.com/
Final URL
https://verifieddr.com
Created
Jun 29, 2026, 2:22 PM
Safe fetch
681 ms
86
out of 100
100
out of 100
92/92 rule points
96
out of 100
73/76 rule points
57
out of 100
54/94 rule points
92
out of 100
101/110 rule points
Category point breakdown
Biggest score-losing checks
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1).
Detected labels or accessible names for 1 of 2 form control(s).
Horizontal overflow: 0px. Small tap targets: 39.
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.57.
What failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1).
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
What failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 1 of 2 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
What failed
Several basic browser protection headers were not visible.
Evidence
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
How to fix it
Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
What failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 39.
Priority
Priority 13: fix during launch polish.
Why it matters
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
How to fix it
Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
What failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.57.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters
Low contrast makes a launch page feel less polished and can exclude users with low vision.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
This scan did not produce unknown checks. If a future page has partial public data, the report will show those checks here instead of guessing.
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1).
Detected labels or accessible names for 1 of 2 form control(s).
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.57.
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Horizontal overflow: 0px. Small tap targets: 39.
Showing failed checks.
These checks need attention.
Detected 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Failed: earned 15 of 18 points from partial coverage.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
Detected labels or accessible names for 1 of 2 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
3 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.57.
Failed: earned 0 of 8 points.
Priority: Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (30), landmark-unique (1).
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Horizontal overflow: 0px. Small tap targets: 39.
Failed: earned 0 of 9 points.
Priority: Priority 13: fix during launch polish.
Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Checked: https://verifieddr.com
Next/final: https://verifieddr.com
Content type: text/html; charset=utf-8
Checked: https://verifieddr.com
Next/final: https://verifieddr.com
Content type: text/html; charset=utf-8
Content hash: 482761c7385791c6cd6e673a67e4b063a52eeae13b5d544cf4c81a57a80bdbd3
Checked: https://verifieddr.com/robots.txt
Next/final: https://verifieddr.com/robots.txt
Content type: text/plain; charset=utf-8
Content hash: 188ef8f3070df6489726cb638f207f1fc831333cf25bb6f90ba971bd808970b8
Checked: https://verifieddr.com/sitemap.xml
Next/final: https://verifieddr.com/sitemap.xml
Content type: application/xml; charset=utf-8
Content hash: 0b6ca89a1450230bc6299244aa741cbf8c217807203064d935f0c2a8dda5743c
Checked: https://verifieddr.com/llms.txt
Next/final: https://verifieddr.com/llms.txt
Content type: text/plain; charset=utf-8
Content hash: ba5218ae2d6bb0ba372f28ae0017bfb03177eb129b8d54bd8dcee38d5a915246
Checked: https://verifieddr.com/.env
Next/final: https://verifieddr.com/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://verifieddr.com/.git/config
Next/final: https://verifieddr.com/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://verifieddr.com/wp-config.php
Next/final: https://verifieddr.com/wp-config.php
Content type: text/html; charset=UTF-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://verifieddr.com/backup.zip
Next/final: https://verifieddr.com/backup.zip
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=utf-8
referrer-policy
strict-origin-when-cross-origin
permissions-policy
camera=(), microphone=(), geolocation=()
x-content-type-options
nosniff
content-security-policy
frame-ancestors 'self' https://buildhop.io https://*.buildhop.io
strict-transport-security
max-age=31536000; includeSubDomains
Share preview
verifieddr.com website audit report
Close to ready: 86/100 overall, with prioritized fixes for SEO, security, accessibility, and design.
Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.