Security

How PageNora keeps your website and your account safe

PageNora is built to look, never to touch. It reads public pages the way a visitor’s browser asks for them, only on websites whose owner has proved control, and it keeps each customer’s data separate from everyone else’s. This page explains how, in plain words.

No system is perfectly secure, and we do not claim any security certification. What follows is what PageNora does today.

Your website

Checks that only read, and only where you allowed them

Read-only by design

A check asks for a public page and reads what your server sends back. It never logs in, clicks a button, submits a form, places an order or changes anything on your website. It does not run your website’s code (JavaScript).

Proof of ownership first

Nothing is checked until you prove you control the website, by publishing a short code as a page, a file or a tag. PageNora re-reads that proof about once a day and pauses checks for the website if it is gone.

Polite and identifiable

Requests identify themselves as PageNoraMonitor/0.1, respect your robots.txt, use https only, and follow at most three redirects, and only within your own website.

Guard rails on every request

  • No private or internal addresses. Before connecting, PageNora looks up every address a website name points to. If any of them is a private, internal or reserved address (for example a home or office network, or the special addresses cloud servers use for their own settings), the check is refused. The connection is then tied to the address that was checked, so it cannot be quietly redirected somewhere else.
  • Size and time limits. A check reads at most about 1 MB of a page and gives up after a set time. A page that is too large or too slow is reported as “unknown”, never as healthy.
  • Each check is kept apart. Every check runs in its own separate process with a time limit. That process cannot see PageNora’s own passwords and keys (for email, billing or the database), so a hostile page has nothing useful to reach.
  • No copy of your site. A check compares your page with what you approved and keeps the findings, not a copy of your pages.

More detail: what PageNora checks, and what it does not.

Your account

No password to steal

  • Emailed sign-in links. You sign in with a link we email to you. It works once and expires after 15 minutes. There is no password, so there is no password to guess, reuse or leak.
  • Stored scrambled. Sign-in links and sessions are stored only in a scrambled (hashed) form, so even someone reading our database could not use it to sign in as you.
  • Strict session cookies. The cookie that keeps you signed in holds only a random code. Scripts on the page cannot read it, it is sent only over a secure connection, and only to PageNora itself, never along with a request started by another website. Each sign-in ends after 30 days at most, or when you sign out.
  • Protection against forged requests. Every change you make in the app (saving a check, removing a website) must carry a secret token from your own session and come from PageNora’s own pages. This stops another website from making changes in your name (a “cross-site request forgery”).
  • Limits on automated abuse. The sign-in form uses Cloudflare Turnstile to tell people from bots, and the number of sign-in requests per network and per address is limited.
  • Sign out everywhere. One button ends every session of your account on every device, cancels any sign-in link you have not used yet and disconnects our WordPress plugin from your account.

Your data

Kept separate, backed up, encrypted

  • Each account walled off in the database. Separation between customers is enforced by the database itself, not only by the app. A database feature called row-level security means each request can only see the rows that belong to the account making it. The app connects with restricted database logins, never as the database administrator, and the database is reachable only on our hosting provider’s private network.
  • Encrypted nightly backups, with an off-site copy. The database is backed up every night. Each backup is encrypted before it leaves our servers, with a key that is not kept on the hosting provider, and an off-site copy is stored separately (on Cloudflare R2), so neither provider can read it. Backups are kept for about 35 days, and we have tested restoring from a real encrypted backup.
  • Limited operator access. Only the PageNora operator can open the operator console. It opens only for the operator’s own address with a sign-in from the last 8 hours, and every change made there is logged.
  • Deletion on your terms. You can delete your websites, pages, saved checks and check history yourself with Reset all settings. Check history is deleted automatically after 12 months. See the Privacy Policy for every retention period.

Payments

PageNora does not take payments yet. Billing is connected to Stripe in test mode only, so no real card can be charged. When paid plans start, card details will be entered on Stripe’s own payment page; PageNora never sees or stores card numbers. We will update the Privacy Policy before any payment is taken, and nothing is charged without your agreement.

Found a problem?

How to report a security issue

If you think you have found a security weakness in PageNora, please tell us through the contact form. Put “Security” at the start of your message and include:

  • what you found, and where (the page or web address);
  • the steps to see it for yourself;
  • what you think someone could do with it.

Please do not look at or change other people’s data, do not run tests that could slow the service down for others, and give us a reasonable chance to fix the issue before you share it. We will reply and tell you what we find. There is no paid reward programme.

If a breach affects you, we will tell you promptly, as the law requires.

Look, never touch. Try it on your own website.

Free plan · No credit card · No end date · Set up in about five minutes