Civicord · UK · Browse / Conservative and Unionist Party / Easington / Joanne Marie Howey

Campaign site for Joanne Marie Howey (Conservative and Unionist Party — Easington), scraped April 2025, audited September 2026.

Joanne Marie Howey

View evidencePropose a correctionIs this your record? Claim itReply if this is wrongMore change stories ↗See what you followQuery The Graph

Snapshot audit, not a current availability check. HTTP success and surname matches do not prove campaign content survived. On-chain fields are on Sepolia testnet; full content is not stored on-chain.

URLs unreachable — Joanne Marie Howey's recorded URLs had DNS or connection failures at the 2026-09-07 audit. This does not establish permanent removal.

Conservative and Unionist Party: 65% responding across the party · this candidate: not responding.See the cohort ↗

Stood in Easington — 0 of 2 sites responding (0%) · 2 unreachable · 0 redirected

E14001211 · North East · England · 70,043 electorate · Halftone: more / larger paper dots = lower response rate.

Also stood in: Bishop Auckland

  1. Apr 2025scraped
  2. Sep 2026audited
  3. PendingSepolia

Propose a correction

If a URL, name, or sentence on this record is wrong, send a sourced request. It is queued for a person to review. It does not change the audit, the April scrape, the sentence comparison, or the Sepolia record.What is verified, and what is not.

Review queue

Requests stored for this record. A request is not an edit.

    Is this your record?

    If you are Joanne Marie Howey or work on their campaign, you can claim this record. Say how a reviewer could verify it — a campaign-domain email, a link on the live site, or your Democracy Club profile. A claim is queued for a person to check; it grants no edit access and changes nothing until verified.

    Content chronology

    transformedLow text overlap with the compared archived page — inspect both sources · 13% of April tokens still found

    Websites

    DNS failurehttps://www.joannehowey.uk

    What changedDNS or connection failure at the audit

    • HTTP result: DNS failure at the 2026-09-07 audit
    • Candidate-name signal: not assessed

    Source evidence and excerpts

    These are short excerpts from the April 2025 scrape, not the later wording and not complete archived pages. Original filenames identify the stored extracts. Browse the Campaign Lab source dataset ↗

    Open the compared Wayback capture ↗

    Scrape excerpts — April 2025 · 8 shown
    PageCharsOpening excerpt
    content_25.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_20.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_23.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_6.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_16.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_8.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_22.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    content_12.html1,451
    When you visit our website, it may store or retrieve information on your browser, mostly in the form of cookies. This in…
    Agent viewInspect the data and verify the recordGraph live

    The audit ledger above is a static snapshot. The buttons below run live queries against The Graph and the ledger JSON — only when you click them. Nothing fetches automatically and nothing here is mocked.

    1 Free ledger JSON

    /api/candidates/79308.json

    Static audit record — websites, status, ENS hint.

    2 WebMCP join

    Preferred agent tool — live Graph + ledger verdict.

    compare_onchain_to_ledger(id="79308")
    -> { onchain, ledger, verdict[] }

    3 The Graph (live)

    On-chain p79308.civicord.eth via/api/graph (Studio proxy) — person id, not seat slug.

    {
      candidate(id: "79308") {
        id ensName status url personName textRecordCount
        registeredAt registeredAtBlock owner
      }
      _meta { block { number } hasIndexingErrors }
    }

    Live queries run on demand; a failure is shown honestly, never replaced with a cached response. Verify independently: ENS ·resolver ·Subgraph Studio ·/api/graph ·openapi.yaml ·source

    Jurisdiction

    Reading…

    Reading the public record…

    Reading /api/… — the same static JSON an agent pays for.

    ↑↓ move · ↵ open · Esc close