NeoShield Scan Free

For freelance developers, WordPress maintenance providers, small agencies and MSP teams

Turn public website security checks into verified client work.

Assess authorized websites, explain the evidence, provide platform-specific remediation, and document whether each correction was confirmed by a rescan.

Free plan: 1 website, 1 scan per month · Email sign-in, no card

Only for websites you own or may assess · Passive checks of public pages and DNS · No exploitation, login testing, brute force, fuzzing or load testing

Website security report

neoshieldsecurity.com

Assessed 2 Nov 2026 · Extended Passive Assessment

100/100 A

Passive Public-Configuration Score · 3 review recommendations pending

This score measures only the passive and authorized checks completed during this assessment. It is not an overall website-security rating or penetration-test result.

0 confirmed findings · 3 review recommendations · 4 informational observations · 32 checks passed · coverage 44 of 45 applicable checks

  1. RR-01 Low robots.txt advertises sensitive-looking paths Review recommendation
  2. RR-02 Low DNSSEC not enabled Review recommendation
  3. RR-03 Low DMARC has no aggregate reporting address Review recommendation
  4. IO-01 Info MTA-STS discovery record not observed Informational
  5. IO-02 Info TLS-RPT not observed Informational

+ 2 more informational observations

Real scan of NeoShield’s own website, 2 Nov 2026.

Only confirmed findings (CF-) reduce the score. Review recommendations (RR-) and informational observations (IO-) do not. The score covers publicly observable configuration only; it is not a penetration test, a certification or a measure of overall security. Scoring model 2026.08-d. How the score works

Report vs_d74d7c310573965e193d2c1b

35-second tour

From a client’s question to a verified fix

See how a NeoShield report answers “Is our website secure?” with evidence instead of a guess: scan, explain, fix and verify.

  1. 0:06 Scan Check a website you are authorized to assess.
  2. 0:11 Explain One clear score, with every item labeled.
  3. 0:16 Fix Step-by-step fixes for your platform.
  4. 0:21 Verify A rescan confirms the fix. Send a client-ready PDF.

Step 2 shows a real scan of NeoShield’s own website. Steps 3 and 4 use the sample report’s demonstration data.

Read the video text
  1. Your client asks: “Is our website secure?” Don’t guess. Show them the work.
  2. NeoShield: website security reports and fix verification for freelancers, agencies and MSPs.
  3. Step 1, Scan: check a website you are authorized to assess.
  4. Step 2, Explain: one clear score, with every item labeled (real scan of NeoShield’s own site).
  5. Step 3, Fix: step-by-step fixes for your platform (demonstration data).
  6. Step 4, Verify: a rescan confirms the fix, then send a client-ready PDF (demonstration data).
  7. Built to be trusted: passive checks of public configuration only, no exploitation, login testing or load testing, and only websites you own or may assess.
  8. Turn public website security checks into verified client work. Scan one website free, no card, email sign-in.
NeoShield in 35 seconds · music, no narration

Sample report preview

Pages from the complete sample report and its PDF. Demonstration data, not a customer’s website.

Findings view: Every finding shows what was observed, on which URL, and why it matters to the business.
Findings view Every finding shows what was observed, on which URL, and why it matters to the business.
Remediation guidance: Hand developers the exact change for the client’s platform instead of a generic warning.
Remediation guidance Hand developers the exact change for the client’s platform instead of a generic warning.
PDF report: Send a report a non-technical client can follow, with the developer detail kept for the developer.
PDF report Send a report a non-technical client can follow, with the developer detail kept for the developer.

One report for the client, the developer and the follow-up

  1. Explain the risk to clients

    Show what was observed, where it was found, how severe it is, and why it matters in language a client can follow.

  2. Give developers an actionable fix

    Provide platform-specific starting points for Nginx, Apache HTTP Server, Microsoft IIS, Cloudflare, WordPress, and AWS CloudFront when applicable.

  3. Verify that the correction worked

    Rescan after deployment and record each finding as resolved, partially resolved, still observed, or unable to verify.

Who NeoShield is for

People who look after other people’s websites and need to show that the work was done.

Freelance web developer

Make maintenance work visible.

The client sees an invoice, not the work behind it. Send a report that shows what was checked, what you changed and which fixes a rescan confirmed.

Read more: Freelance web developer

WordPress maintenance provider

Support the care-plan renewal.

Attach a report per website to the monthly update, with WordPress fix steps and scheduled scans that flag a setting that changed after a plugin or hosting update.

Read more: WordPress maintenance provider

Small web agency

Spend less time writing reports.

Each finding carries a plain explanation for the client and a platform fix for the developer, so nobody rewrites the same advice for every website.

Read more: Small web agency

Small MSP team

Catch regressions across many websites.

Monitor client websites as often as daily on MSP / Team (early access), with report history per website and up to 5 users.

Read more: Small MSP team

From finding to verified fix

One finding from the sample report: what was observed, how to explain it, the fix for the client’s platform, and the rescan that confirms it. Demonstration data

CF-02 High

Strict-Transport-Security header missing

Observation
HTTPS is available, but the response carries no Strict-Transport-Security header. https://www.client-shop.example/
Client explanation
HSTS tells browsers to always use HTTPS for this site, closing the window in which a first request can be downgraded to HTTP.
Remediation
Send Strict-Transport-Security in stages: five minutes, then one day, then one year once HTTPS is stable. Add includeSubDomains only when every subdomain serves HTTPS.

Configuration for the client’s platform

Nginx

# server { } block (or http { })
add_header Strict-Transport-Security "max-age=300" always;

Reload with: nginx -t && systemctl reload nginx. add_header in a location block replaces headers set at server level.

Apache HTTP Server

# Requires mod_headers (a2enmod headers)
Header always set Strict-Transport-Security "max-age=300"

Place in the VirtualHost or .htaccess, then run apachectl configtest and reload.

Microsoft IIS

<!-- IIS 10 (version 1709+): applicationHost.config, inside the <site> element for this website -->
<!-- Stage 1: five minutes. Raise max-age in stages (see the rollout steps). -->
<hsts enabled="true" max-age="300" includeSubDomains="false" redirectHttpToHttps="true" />

Native HSTS support is available from IIS 10 version 1709. On older versions, add the header with customHeaders.

Cloudflare

SSL/TLS > Edge Certificates > HTTP Strict Transport Security (HSTS) > Enable HSTS
1. Max Age: start with the shortest value offered
2. Include subdomains: off for now; turn on only when every subdomain serves HTTPS
3. Preload: off
4. Save, then raise Max Age in stages

Cloudflare does not offer five minutes, so the first stage is longer than on your own server. Make sure HTTPS works everywhere before enabling it.

WordPress

<?php
// In a small site-specific plugin (or the child theme's functions.php)
add_action( 'send_headers', function () {
    header(
        "Strict-Transport-Security: "
        . "max-age=300"
    );
} );

Setting the header in the web server or CDN is preferred; use this when you only control WordPress.

AWS CloudFront

CloudFront > Policies > Response headers > Create response headers policy
1. Security headers > Strict-Transport-Security: max-age 300 (raise in stages), includeSubDomains off
2. Origin override: enabled
3. Attach the policy to the distribution's cache behavior(s)

Changes propagate to all edge locations within a few minutes.

Starting points, not finished changes: AI-assisted and template guidance can be incomplete or wrong. Review and test in staging before production.

Verified fixed by a rescan on 8 Oct 2026

Score on 1 Oct 2026
55 D
After 2 fixes were verified
73 C
Still open, in priority order
4

A finding is marked resolved only when a scan confirms it, and it reopens automatically if it comes back. Demonstration data.

How it works

One repeatable workflow for every client website you manage.

  1. Confirm authorization

    Confirm you own the website or have permission to assess it. Nothing runs before this.

  2. Assess

    A passive check of public pages and DNS: HTTPS, TLS, security headers, cookies, exposed files, SPF, DMARC and security.txt.

  3. Review

    Findings are ordered by priority, each with the evidence observed and why it matters.

  4. Share

    Send the client a readable report and the developer the fix for their platform. PDF reports on paid plans.

  5. Verify

    After the fix is deployed, Verify Fix rescans and records each finding as resolved, partly resolved, still observed or unable to verify. Paid plans.

  6. Monitor where supported

    Scheduled scans flag a fixed setting that comes back: weekly on Pro, up to daily on MSP / Team.

Not a penetration test, a professional security audit, a compliance audit or a certification. A clean result does not prove a website has no vulnerabilities. Coverage and limitations

Included with Pro and MSP / Team

Two AI assistants for the security work around your reports

Both assistants reply in English or in Japanese. Answers are drafts for a person to review, sized to the evidence you give, and limited to defensive security.

AI SOC Copilot Labs

Find out why a risk score or alert changed

Paste sanitized alert fields or a score breakdown. The copilot separates what the evidence shows from what it does not, lists possible causes and gives one next step. With no evidence it gives a short answer and asks for what it needs instead of guessing.

  • Answer length follows the evidence: a short answer without it, a full triage with it.
  • Evidence is treated as untrusted data, and injection attempts are flagged.
  • No severity, ATT&CK mapping or containment advice without evidence. Containment always needs human approval.
  • Query drafts only when the platform and data source are known.

Try asking “Why did the risk score increase?”

Open the AI SOC Copilot

AI Security Consultant Labs

Get an incident-response plan and a tabletop exercise

Describe your organization, or start with nothing. You get a baseline plan right away, with stated assumptions and up to five questions to tailor it, aligned with NIST CSF 2.0 and NIST SP 800-61 Rev. 3.

  • A roadmap for days 1 to 30, days 31 to 90 and months 4 to 6.
  • A tabletop exercise with timed injects, evaluation criteria, owners and deadlines.
  • Japan considerations: APPI and the PPC, JPCERT/CC, IPA, and the FSA for financial services.
  • Notification points to confirm with counsel, not legal conclusions.

Try asking “How do I get incident-response ready, including a tabletop exercise plan?”

Open the AI Security Consultant

AI output is advisory and needs human review. It is not legal advice, does not confirm a compromise, and does not run queries or change your systems. The text of questions and answers is not written to logs. Compare plans

Plans

Prepaid passes for 30 or 365 days. No automatic renewal.

Free

¥0

1 website · 1 manual scan per month · up to 3 medium-severity findings in full per scan · 1 user

Pro

¥1,980 / 30 days

Up to 5 monitored websites · 100 manual scans per month · weekly monitoring · 1 user

MSP / Team Early Access

¥7,980 / 30 days

Up to 25 monitored websites per included user · 100 manual scans per month · monitoring as often as daily · 5 users

Planned: Separate client workspaces with per-client access, Agency logo branding on reports, Monthly executive summaries

Compare plans and limits

Separate checks and a hand-built report, or one workflow

SecurityHeaders, Qualys SSL Labs and MXToolbox are useful at the test each one runs, and SSL Labs tests TLS in more depth than NeoShield. Keep using them. NeoShield adds the work around the checks: one report a client can read, fixes for the client’s platform, verification of each fix, and history per website.

NeoShield compared with three free security checkers
Feature SecurityHeaders SSL Labs MXToolbox NeoShield
Security checksHTTP security headersTLS and certificates, in depthDNS, mail server and blocklist lookupsHeaders, TLS, cookies, exposed files, SPF and DMARC in one report
Client-ready reportResults pageResults pageResults pagePDF reports a client can read (Pro, Team)
Remediation guidanceHeader explanationsRatings and protocol detailProblem descriptionsFix steps for Nginx, Apache, IIS, Cloudflare, WordPress and CloudFront
Fix verificationRun the test again and compare by handRun the test again and compare by handRun the test again and compare by handVerify Fix records each finding as resolved, partly resolved or still present
MonitoringNot part of the free testNot part of the free testSold separately for DNS and emailScheduled scans that flag regressions (Pro, Team)
Report historyNot organized by client websiteNot organized by client websiteNot organized by client websiteThe 100 most recent reports per account, by website
Agency workflowOne check, one website at a timeOne check, one website at a timeOne check, one website at a timeClient list, Security Center and shared seats (Team)
PriceFreeFreeFree lookups; paid plans for monitoringFree plan; Pro ¥1,980 per 30 days

Based on the public free versions of each tool as of November 2026. Product names belong to their owners; NeoShield is not affiliated with them. Use them alongside NeoShield. If something here is out of date, tell us and we will correct it. Report a correction

What you are buying from

A new product, launched in 2026. Customer stories and usage figures will appear only when they are real and approved.

Who runs it
Operated from Japan, with support by email. Scans, monitoring and payments run automatically. About NeoShield
Payment
Card details are entered on Stripe-hosted pages. Passes are prepaid and never renew automatically.
Data retention
The 100 most recent reports per account are kept; security logs are removed after 30 days. Details
Support
Email only, no live chat or SLA. Pro replies aim for 2 business days.
Certification
No SOC 2 or ISO/IEC 27001 certification is held or implied.
Subprocessors
Hostinger (hosting), Stripe (payments), Anthropic (optional AI), Google and PostHog (analytics, only with consent).

Frequently asked questions

Is it a penetration test?

No. NeoShield checks publicly observable configuration on websites you are authorized to assess: HTTPS and TLS, security headers, cookies, server disclosure, commonly exposed files, SPF, DMARC and security.txt. It does not exploit, log in, brute force, fuzz or load test, and it does not review source code or internal systems. It is not a professional security audit, a compliance audit or a certification, and a clean result does not prove a website has no vulnerabilities.

Which websites may I scan?

Only websites you own or have permission to assess, such as client websites covered by your service agreement. You confirm this before every scan and every recurring schedule.

What does the free plan include?

One website and one manual scan per month. Every finding is named, with its severity, affected host, basic evidence and why it matters, and up to three medium-severity findings are shown in full. Complete evidence, platform-specific fixes, exports, Verify Fix, history and monitoring are part of the paid plans.

Can I send the report to my client?

Paid plans export each report as a PDF that you can share with a client or developer, with optional "Prepared for" and "Prepared by" names. Reports carry NeoShield branding today. Agency branding is planned.

How does Verify Fix work?

After the fix is deployed, run Verify Fix on the report (Pro and MSP / Team). NeoShield scans the same website again and records an outcome for each finding: resolved, partially resolved, still present, or unable to verify. A finding is only marked resolved when a scan confirms it, and it reopens automatically if it comes back.

Do paid plans renew automatically?

No. Paid access is currently sold as prepaid passes for a fixed period (30 or 365 days) with no automatic renewal. When the period ends, the account returns to the Free plan unless you buy another pass.

Who runs NeoShield?

NeoShield is operated from Japan. Support is by email only, with no live chat, phone or SLA; Pro replies aim for two business days. Scans, scheduled monitoring and payments run automatically, so they do not wait for a support reply.

Show your next client what was checked and what you fixed.

Start with one website you are authorized to assess, or read the full sample report first.

Free plan: 1 website, 1 scan per month · Email sign-in, no card

Only for websites you own or may assess · Passive checks of public pages and DNS · No exploitation, login testing, brute force, fuzzing or load testing