Website profiles · Technology insights · Alternatives

scabard.com

Paid content
Visit website
Profile views 7 Outbound visits 13 Normal
Scabard Full homepage screenshot

At a glance

Category
Games & Board Games
Language
English
Paid-content signal
Paid contentObserved
Registered
2012
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Scabard?

Scabard is an online campaign manager for tabletop role-playing games, aimed at Game Masters who want their world to behave like a connected setting rather than a folder of loose notes. Its central idea, stated on its own pages, is that "your campaign is not a pile of pages": characters, places, factions, events, maps, and history are linked to each other, so a faction page can list its members and a location can sit inside a larger region. It also supports campaign history through timelines, arcs, and session notes, plus hidden pages and secret notes so GM-only material stays out of players' view until you reveal it.

Who it suits

  • GMs running long campaigns where remembering who met whom six sessions ago has become a chore.
  • World-builders who enjoy developing NPCs, factions, and lore between sessions and want prompts that push them to flesh out details.
  • Groups with co-GMs or trusted collaborators, since material can be shared selectively rather than handed over wholesale.
  • GMs with curious players, who can publish a spoiler-free view of the setting while keeping twists hidden.

Where it fits less well

If you run short, self-contained adventures, or you already work happily in a plain document or wiki you control, the structure may feel like overhead. A connected database rewards campaigns that accumulate material; it offers less for a one-shot.

A practical test

Take your current campaign's five most important NPCs and ask whether you can see, at a glance, which faction each belongs to and which events they were involved in. If that takes more than a minute of digging, a linked campaign tool is worth trialling. Scabard offers a free sign-up, with paid tiers listed on its Pricing page, so you can build a small test world before committing. For comparison, Obsidian is a general note tool many GMs adapt for this purpose, and World Anvil is a dedicated world-building platform; both are reasonable alternatives if you want a different balance of flexibility and structure.

How does Scabard help Game Masters organize NPCs and campaign notes?

Scabard is built around the idea that a campaign is a web of connected people, places, factions, and events rather than a folder of separate documents. For Game Masters, that means NPCs and notes are stored as linked entries: a character can belong to a faction, live in a place, and be tied to events on a timeline, so the relationships stay visible instead of being buried in prose.

NPC organization

  • Characters, places, factions, and events live in one connected world, so an NPC page can reference the faction they serve and the location they operate in.
  • The page evidence notes that the structure "forces you to ask questions of your NPCs that bring your world to life" — a reviewer observation quoted on the site, not a neutral test. In practice, that kind of prompting helps if you tend to create names without motives, but it can feel like extra homework if you prefer improvising NPCs at the table.
  • Hidden pages and secret notes let you keep villain motives or plot twists visible to you while players see a spoiler-free version.

Campaign notes and continuity

  • Timelines, arcs, and session notes address the "what happened six sessions ago" problem by keeping events in chronological context.
  • Because events link to the characters and places involved, you can trace who was present and where, rather than searching several documents.
  • Maps, notes, characters, and AI-assisted ideas are gathered in one place, according to the site, which reduces tool-switching.

Sharing and secrecy

  • You can share your world with trusted collaborators without exposing player-facing secrets.
  • Players can be given a view of what they should know, while GM-only material stays hidden.

Trade-offs

Approach Strength Weakness
Scabard's connected entries Relationships and continuity stay visible; secrets are manageable Requires upfront linking and maintenance
Plain notes or documents Fast, familiar, no setup Connections get lost as the campaign grows; spoiler control is manual

A practical next step: pick one faction and three NPCs from your current campaign, create their entries, and link each NPC to the faction and a location. If the links reveal a relationship or motive you had forgotten, the connected approach is earning its keep; if you find yourself fighting the structure, a lighter note system may suit your table better. See Scabard for the feature details.

Can I keep parts of my campaign world hidden from my players in Scabard?

Yes. Scabard is built around the idea that a Game Master can expose some parts of a campaign world while keeping others private. Its page evidence describes hidden pages, secret notes, and spoiler-free connections that only you can see until you decide the time is right, plus sharing with trusted collaborators without spoiling players. So the practical model is selective visibility rather than one all-or-nothing public wiki.

H3 What that looks like in practice

  • Player-facing content: the places, factions and history you want players to read and ask about.
  • GM-only content: NPC motives, hidden identities, future plot turns and notes you don't want revealed.
  • Connections that don't leak: a public page can link to a secret one in a way that stays invisible to players.
  • Trusted collaborators: co-GMs or a worldbuilding helper can see more than the player group.

H3 A concrete scenario You publish a capital city page for your players, listing districts and notable taverns. Behind it, you keep a hidden page for the thieves' guild that actually runs the docks, with secret notes on which NPCs are members. When a player asks about the harbormaster, you have the answer ready without exposing the guild. Later, when the reveal happens, you make that page visible.

H3 Decision criteria Choose Scabard if your main problem is continuity and secrets across a long campaign, and you want your world stored as connected people, places and events rather than loose documents. Look elsewhere if you mainly need a battle map with tokens and rules automation; Scabard's emphasis here is world organization and controlled reveal, not running tactical combat.

Next step: before importing everything, sketch your visibility plan. List the handful of secrets that must stay hidden and decide which pages are player-visible, GM-only, or collaborator-only. That mapping is what makes the hidden-page feature useful instead of just another pile of notes. If you also want to see how other campaign managers handle player-facing wikis, compare with Obsidian and World Anvil, keeping in mind that each tool draws the public/private line differently.

How do I share my Scabard campaign with co-GMs or players without spoiling secrets?

Scabard is built around exactly this problem: you can share parts of a campaign world while keeping hidden pages and secret notes invisible to the people you share with. The GM controls what each viewer can see, so co-GMs and players can get different views of the same world.

Sharing with players

  • Share only the pages players should know: public places, known NPCs, factions they've met, and lore their characters would reasonably have learned.
  • Keep spoiler material on hidden pages or in secret notes. Those stay GM-only until you choose to reveal them.
  • Use spoiler-free connections so a public page can link to something relevant without exposing the secret behind it.
  • Expect players to ask about your world; a curated player-facing view gives them something to read without you answering the same questions every week.

Sharing with co-GMs

  • Co-GMs typically need the fuller picture: hidden pages, timelines, arcs, and notes. Share that layer with trusted collaborators rather than with the whole table.
  • The risk here is accidental exposure, not malice. Decide in advance which pages are player-safe and which are GM-only, and keep that boundary consistent as the campaign grows.
  • If you run multiple campaigns or arcs, keep secrets scoped per campaign so a co-GM in one doesn't see spoilers for another.

A practical setup

  1. Build the world with everything visible to you, including secrets.
  2. Mark each page as player-facing or GM-only as you create it, not later.
  3. Share the player view with your table and the GM view with co-GMs.
  4. When a secret is revealed in play, flip that page to player-visible instead of rewriting it.

Next step

Before your next session, pick the five pages your players are most likely to ask about and confirm each one is either safely public or properly hidden. That small audit catches most accidental spoilers.

For a broader look at how Scabard handles world-building and campaign organization, see Scabard. If you also want a general reference for running shared campaign wikis, Obsidian and Notion are common alternatives, though neither is purpose-built for GM-versus-player visibility the way Scabard describes itself.

Does Scabard offer a free plan, and what do the paid upgrades cost?

Scabard does not publicly present a free plan with a fixed feature set; instead, its homepage invites you to "Sign-Up for Free" and "Start Building Your World," which suggests you can begin using it at no cost. The site also has a separate Pricing page, which is where any paid tiers and upgrade costs would be listed. Because the specific prices and what each tier includes are not shown here, treat the free sign-up as an entry point and check the pricing page directly for current numbers.

Practical next step: Create a free account, build one small test campaign (a handful of NPCs, one location, one faction), and see whether the free level covers your needs. If you hit limits on campaigns, storage, collaborators, or secret/hidden content, that is the signal to compare paid tiers. Upgrade costs and tier names change, so verify them on the official pricing page rather than relying on secondhand summaries.

Decision criteria for paying:

  • Number of active campaigns — if you run several games at once, free limits may bind quickly.
  • Collaborators and player sharing — if you need trusted co-GMs or player-facing pages without spoilers, check which tier unlocks sharing controls.
  • Secrecy features — hidden pages and secret notes matter most for mystery-heavy games.
  • Long-term continuity — if you expect a multi-year campaign, paying for organization and history tools is easier to justify than for a one-shot.

How do timelines and relationship links in Scabard help track campaign history across sessions?

Scabard treats campaign history as a connected web rather than a folder of session notes. Timelines and relationship links are the two mechanisms that make that work: timelines give events a chronological spine, while links tie each event to the characters, places and factions involved.

Timelines: the chronological spine

A timeline entry records what happened and when, so a session six weeks ago is retrievable by position rather than by memory. Because entries sit alongside arcs and notes, you can see a run of sessions as one continuing storyline instead of isolated recaps. This matters most when players ask "wait, didn't we already deal with this?" — you can check the sequence rather than reconstruct it from chat logs.

Relationship links: the who and where

Links connect entities to each other: characters belong to factions, places contain other places, and events shape history. When you open an NPC, you see the factions, locations and events they touch, which surfaces connections you may have forgotten you created. Scabard's own framing is that continuity becomes easier because relationships stay visible instead of getting buried in notes.

Why the combination helps across sessions

Need What carries the weight
What happened, and in what order Timeline entries and arcs
Who was involved, and where Relationship links between characters, places, factions and events
Keeping reveals hidden Hidden pages, secret notes and spoiler-free connections
Sharing without spoiling Selective sharing with trusted collaborators

The practical effect: prep for the next session starts from the existing web rather than a blank page, and new material attaches to what is already there.

A concrete scenario

Suppose a player asks why a merchant won't deal with them. You open the merchant, follow links to the faction they belong to, then to the event where that faction was wronged — and you have an answer consistent with what actually happened at the table, without rereading three sessions of notes.

How to decide if it fits

Timelines and links pay off when your campaign has enough recurring NPCs, factions and long-running threads that memory alone fails. For a short arc with a handful of characters, a simple document may be less overhead. One reviewer noted that Scabard "forces you to ask questions of your NPCs that bring your world to life," which points to its real strength: prompting connective detail rather than just storing it.

Next step: pick one faction from your current campaign and add its members, home base and one defining event, then link that event to the session where it occurred. If the resulting page tells you something you'd forgotten, the approach is earning its keep.

Related questions

More questions →
How Does Scabard Help Organize NPCs, Places, Factions, and Events?

Scabard is a campaign manager for tabletop RPG Game Masters that treats your world as a connected web rather than a pile of separate pages. Instead of storing NPCs, locations, factions, and events as isolated notes, it lets you link them so that characters belong to factions, places contain other places, and events shape history. This approach suits GMs running campaigns that have grown complex enough that scattered notes no longer work — typically once you have too many NPCs to track, can't recall what happened six sessions ago, or need to keep secrets from players while still sharing parts of the world.

The core idea: a connected world, not a pile of pages

Scabard's stated design principle is that "your campaign is not a pile of pages." It models your setting as a living web of people, places, factions, events, secrets, maps, and history, where everything connects. The practical effect is that relationships stay visible instead of getting buried in notes.

This matters most when a campaign reaches the point where continuity breaks down. The site frames these as recurring "sound familiar?" moments:

  • Too many NPCs to keep track of
  • Can't remember what happened six sessions ago
  • Keeping mysteries secret is getting difficult
  • Notes are scattered across too many places
  • Players ask about your world and you want a clean way to answer

How the four entry types relate to each other

Scabard organizes content around interconnected entries. Based on the site's description, the relationships work like this:

Entry type How it connects
Characters (NPCs) Belong to factions and appear in places; relationships between them stay visible
Places Can contain other places, forming a hierarchy
Factions Group characters and tie them to the wider world
Events Shape history and connect to the people and places involved

Because these links are explicit, you don't have to re-explain context every time you open a page — the connections carry that context for you.

Keeping history and continuity straight

Scabard supports an interactive campaign history built from timelines, arcs, and notes. This is aimed at the "what happened six sessions ago" problem: instead of reconstructing events from memory or a chat log, you record them as events that link back to the characters and places involved. Updates and notes accumulate on the relevant entries, so continuity becomes easier to maintain as the campaign runs.

Managing secrets and player-facing information

A recurring concern for GMs is keeping mysteries hidden while still sharing what players should know. Scabard addresses this with:

  • Hidden pages and secret notes — content only you can see until you choose to reveal it
  • Spoiler-free connections — links that don't leak information to players
  • Selective sharing — share your world with trusted collaborators without accidentally spoiling it for your players
  • Player-facing views — show players what they should know while keeping your secrets hidden

This is the feature set most relevant if your main pain point is information control rather than organization alone.

Starting small and letting the world grow

Scabard is designed to scale from a few pages upward: you start with a small set of entries and expand as the campaign develops, rather than front-loading an entire world. The site also mentions bringing maps, notes, characters, and AI-assisted ideas together in one place, so worldbuilding and session prep live in the same system.

Who this fits

Scabard is built for Game Masters running campaigns with enough moving parts that continuity and secrecy have become real problems. If you run short, self-contained sessions with few recurring NPCs, a simple notes app may be enough. If your campaign has a growing cast, multiple factions, layered locations, and a history you need to keep straight — and players who ask questions about your world — Scabard's connected-entry model is aimed directly at that situation.

The site offers a free sign-up and a separate pricing page for paid tiers, so you can evaluate the core organization model before committing.

What is Scabard and who is it for?

Scabard is an RPG campaign manager for tabletop Game Masters who need to keep a long-running world organized. Its core idea is that a campaign is not a pile of pages but a connected web of characters, places, factions, events, secrets, maps, and history. If your notes have grown past the point where you can remember who knows whom and what happened six sessions ago, Scabard is built for that situation.

What Scabard actually does

Scabard treats your world as a set of linked entries rather than flat documents. Characters belong to factions, places contain other places, and events shape history, with those relationships staying visible instead of getting buried in notes.

The site highlights these recurring pain points it is designed to solve:

  • Too many NPCs to track — organize characters, places, factions, and events into one connected world.
  • Forgetting earlier sessions — build an interactive campaign history with timelines, arcs, and notes.
  • Protecting mysteries — use hidden pages, secret notes, and spoiler-free connections that only you can see until the right moment.
  • Sharing without spoiling — bring in trusted collaborators without accidentally revealing player-facing secrets.
  • Scattered notes — gather maps, notes, characters, and AI-assisted ideas in one place.
  • Player engagement — present interconnected people, places, history, and lore so players care more about the world.
  • Player questions — share what players should know while keeping your secrets hidden.

Who it is for

Scabard is aimed at Game Masters running campaigns ambitious enough to need continuity management. The site's framing — "Loved by Game Masters building rich worlds" — and its feature set point to a few clear fits:

You are… Scabard fits if…
A GM running a long campaign You need timelines, arcs, and notes to recall what happened and who was involved
A world-builder You want factions, places, and history to connect rather than sit in separate files
A GM with secrets You need hidden pages and spoiler-free links you control
A GM working with others You want to share the world with collaborators without leaking plot
A new GM You can start with a few pages and expand as the campaign grows

It is less suited to someone who only needs a plain note-taking app or a one-shot session with no continuity to maintain.

How it differs from a notes app

The distinction Scabard draws is structural: a notes app stores pages, while Scabard stores relationships. Continuity becomes easier because timelines, arcs, notes, and updates are tied to the same connected world, so you can trace what happened, where, and who was involved. The world is also meant to grow naturally — start small, then expand.

Practical notes

  • Sign-up for free is offered on the site, and there is a separate Pricing page with an upgrade path, so a paid tier exists alongside free entry.
  • PayPal is listed as a payment platform.
  • The site also references AI-assisted ideas as part of bringing material together.

If you want to judge fit quickly, the useful test is whether your current campaign has at least one of the "sound familiar" problems above — too many NPCs, lost session history, or secrets getting hard to manage. If none apply, a simpler tool will likely do.

How Does Scabard Track Campaign History and Timelines?

Scabard tracks campaign history by treating your world as a connected web rather than a stack of session notes. Events, timelines, arcs, and notes live alongside the characters, places, and factions they involve, so you can reconstruct what happened, where it happened, and who was there. This fits Game Masters running ongoing campaigns who have lost track of details from earlier sessions and want continuity without digging through scattered files.

The core idea: history is connected, not filed away

Scabard's own framing is that "your campaign is not a pile of pages." Instead, it organizes interconnected characters, places, factions, events, and history so the campaign "grows naturally instead of becoming a collection of scattered notes."

That matters for history tracking because an event is not stored in isolation. When you record something that happened, it can be tied to the people, locations, and factions involved. Later, when a player asks "who was that NPC we met in the northern town?", the answer is reachable through the connections rather than through a keyword search across old documents.

What Scabard uses to build campaign history

Based on the site's described features, history is assembled from several linked elements:

  • Timelines — a chronological spine for your campaign.
  • Arcs — story threads that group related events across sessions.
  • Notes and updates — running records you add as the campaign progresses.
  • Events — discrete happenings that shape history.
  • Connected entities — characters, places, and factions that events attach to.

The stated purpose is continuity: "Timelines, arcs, notes, and updates help you remember what happened, where it happened, and who was involved."

How this solves the "what happened six sessions ago?" problem

Scabard explicitly names this as one of the moments it is built for: "Can't remember what happened six sessions ago? Build an interactive campaign history with timelines, arcs and notes."

In practice, that means you are not relying on memory or on re-reading raw session logs. You maintain a structured history as you play, and the structure does the recall work for you. Because events link to characters, places, and factions, a single event page can surface the surrounding context — who was present, which location it occurred in, and which faction's plans it advanced.

Keeping history consistent as the world grows

The site describes the world as "a living web of people, places, factions, events, secrets, maps, and history," where "everything connects." Two consequences for history tracking:

  1. Relationships stay visible. Characters belong to factions, places contain other places, and events shape history — so the historical record reflects those relationships instead of burying them in prose.
  2. The world can expand incrementally. Scabard suggests starting with a few pages and expanding over time, which suits campaigns whose backstory accumulates session by session.

Handling secrets inside your history

Campaign history often contains information players should not see yet. Scabard addresses this with hidden pages, secret notes, and spoiler-free connections that only the GM can see "until the time is right." It also supports sharing the world with trusted collaborators "without accidentally spoiling it for your players."

This matters for timelines specifically: you can record the true sequence of events — including hidden causes and secret factions — while exposing only the player-facing version.

What to expect and where to check details

The site presents these as core capabilities rather than a step-by-step tutorial, so the exact mechanics of creating a timeline entry or linking an event are best confirmed directly in the product. Scabard lists Campaigns, World-Building, Community, Help, Features, and Pricing in its navigation, and offers a free sign-up path ("Sign-Up for Free"). Pricing details and any paid tiers are available on its Pricing page; the site also indicates PayPal as a payment method.

If your goal is simply to stop losing track of campaign history, the relevant starting point is the timeline, arc, and event tools described above — begin with a few entries, link them to existing characters and places, and let the connections accumulate.

Can Scabard Be Shared With Players or Collaborators?

Yes. Scabard supports two distinct kinds of sharing: you can invite trusted collaborators into your world without exposing secrets to players, and you can share a player-facing view of what they should know while keeping the rest hidden. Both are built on the same visibility controls that let you mark pages, notes, and connections as secret until you decide otherwise.

Two audiences, two sharing modes

Scabard's own feature list separates these use cases, and the distinction matters when you set up a campaign.

Audience What they see What stays hidden
Trusted collaborators (co-GMs, co-writers) Your world as you build it, so they can add and edit alongside you Nothing from them by default — they are inside the world
Players Only the pages and connections you choose to reveal Hidden pages, secret notes, and spoiler-free connections you haven't published

The site frames the collaborator case as "share your world with trusted collaborators without accidentally spoiling it for your players," and the player case as "share what players should know while keeping your secrets hidden." So the same world can serve both groups at once, as long as you keep the visibility settings straight.

How the secrecy actually works

Scabard treats a campaign as a connected web of characters, places, factions, events, secrets, maps, and history rather than a stack of separate pages. That structure is what makes selective sharing possible:

  • Hidden pages stay invisible to anyone you haven't granted access to.
  • Secret notes attach to entities without appearing in the shared view.
  • Spoiler-free connections let you link two things together in your own view without revealing the relationship to players.
  • Reveal timing is yours — the site describes keeping a page hidden "until the time is right," so you can open things up mid-campaign as events unfold.

Because relationships stay visible to you (characters belong to factions, places contain other places, events shape history), you don't lose track of what's connected just because part of it is hidden from players.

Why share with players at all

The stated goal is engagement: "Wish your players cared more about your world?" Scabard's answer is to bring the campaign to life through interconnected people, places, history, and lore, then let players see the parts that are theirs to know. A player-facing view gives them something to read between sessions and a reason to ask questions about your world — without you having to hand over your notes.

Practical setup

  1. Build your world first, marking anything sensitive as hidden or secret as you go.
  2. Decide who each person is: a collaborator who edits, or a player who only reads what you reveal.
  3. Share the appropriate view, then check it as that person would see it before sending the link.
  4. Reveal hidden pages and connections over time as the story reaches them.

The main risk is the obvious one: if you mark something as visible by mistake, it's visible. Reviewing the shared view before you send it is the simplest safeguard.

What to check before committing

Scabard offers a free sign-up and a separate pricing page, so you can test the sharing and visibility controls before paying for anything. The site also lists PayPal among its payment options. Feature availability and any limits tied to a paid tier aren't spelled out in the material here, so confirm the specifics on the pricing page if sharing at scale matters to you.

How Does Scabard Help Game Masters Keep Secrets from Players?

Scabard keeps GM-only material out of player view by treating secrecy as a property of the content itself, not a separate document. You write hidden pages, secret notes, and spoiler-free connections inside the same campaign world your players see, and Scabard controls what each audience can access. This works if you are running a campaign with mysteries, unrevealed NPC motives, or behind-the-scenes history you want to develop before the table learns it.

The core mechanism: visibility is attached to the page

Scabard's model is that your campaign is a connected web of people, places, factions, events, secrets, maps, and history — not a pile of pages. Because each element is a page with its own visibility, you decide per item whether it is GM-only or player-facing. A faction page can exist, be linked from other pages, and still stay hidden until you reveal it.

This differs from keeping a separate "GM notes" file. In a separate file, the secret is invisible to players but also disconnected from the world it belongs to. In Scabard, the secret lives in the same structure, so when you finally reveal it, the connections are already in place.

What the secrecy tools do

Scabard's campaign-growth section names four situations that map directly to keeping secrets:

  • Hidden pages — pages only you can see until you choose to reveal them.
  • Secret notes — notes attached to the campaign that stay out of player view.
  • Spoiler-free connections — links between pages that do not expose the hidden content behind them. A player can see that two things are related without seeing why.
  • Selective sharing with collaborators — you can share your world with trusted co-GMs or collaborators without accidentally spoiling it for your players.

The practical effect: you can build a mystery in public-facing structure while the answer sits in a hidden page, and the two stay linked for your own reference.

Keeping secrets while sharing with collaborators

The risk with co-GMs and collaborators is not players reading your notes — it is a collaborator seeing something they should not, or a player-facing share accidentally including GM material. Scabard addresses this by letting you share your world with trusted collaborators separately from what players see. The same visibility control that hides a page from players also governs what a collaborator can reach, so you do not have to maintain two versions of the campaign.

Revealing information at the right time

Because hidden content is already connected to the visible world, revealing it is a visibility change rather than a copy-and-paste job. When the moment arrives, you make the page or note visible and the connections you built earlier are already there. This is the payoff of the connected-web approach: you prepare the reveal while it is still secret, and the world does not need to be restructured when the secret comes out.

What to check before relying on it

  • Confirm which visibility settings apply to pages versus notes, since the two are described separately.
  • If you share with collaborators, verify what a collaborator account can actually see before inviting someone who is also a player.
  • Scabard offers a free sign-up and a separate pricing page, so check current plan limits on sharing and collaborators before committing a large campaign.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2012, this domain has about 13 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is NameCheap, Inc., a widely used domain service provider. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. Debug-related headers are present: x-debug-header-cf, x-debug-header-cn, x-debug-header-lb. Check whether they are needed in production. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Tailwind CSS, Google Analytics, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. Open Graph is partially configured; og:description, og:image is missing. The title has 30 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.26.14.112

Registration details

RDAP / WHOIS

RegistrarNameCheap, Inc.
Registered2012-12-10
Expires2027-12-10
Domain statusclient transfer prohibited
Nameserversjonah.ns.cloudflare.com、kara.ns.cloudflare.com
DNSSECsigned

DNS records

DNS

TypeNameValueTTLPriority
Awww.scabard.com104.26.14.112300—
Awww.scabard.com104.26.15.112300—
Awww.scabard.com172.67.72.17300—
AAAAwww.scabard.com2606:4700:20::681a:e70300—
AAAAwww.scabard.com2606:4700:20::681a:f70300—
AAAAwww.scabard.com2606:4700:20::ac43:4811300—
MXscabard.comaspmx.l.google.com36001
MXscabard.comalt1.aspmx.l.google.com36005
MXscabard.comalt2.aspmx.l.google.com36005
MXscabard.comalt3.aspmx.l.google.com360010
MXscabard.comalt4.aspmx.l.google.com360010
NSscabard.comjonah.ns.cloudflare.com86400—
NSscabard.comkara.ns.cloudflare.com86400—
TXTscabard.comamazonses:79OqlVsTtb036DLZ5XO7shs8AQcRW9VDQReHr9lOa+I=300—
TXTscabard.comv=spf1 include:_spf.google.com ~all300—
DSscabard.com2371 13 2 5d2452a8822cfc066982722009d9a885e3b8d38e8b20748300c635c15fb863a886400—
DMARC_dmarc.scabard.comv=DMARC1; p=none; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectscabard.com
IssuerGoogle Trust Services
Valid until2026-12-27T02:13 · Remaining when checked: 87 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html;charset=UTF-8
servercloudflare
set-cookieRedacted

Identified technologies

Tailwind CSSGoogle AnalyticsCloudflare

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected
All bots 5 allowed · 16 disallowed
  • Allow/pbs/user/new
  • Allow/pbs/campaign/new
  • Allow/user/stolph/image/
  • Allow/user/taroncreator/image/
  • Allow/user/*/featured-image/
  • Disallow/campaign/
  • Disallow/campaign/*
  • Disallow/pbs/campaign/*/toc_list_item
  • Disallow/pbs/campaign/*/card_list_item
  • Disallow/pbs/campaign/*/connection_list_item
  • Disallow/pbs/campaign/*/connedit
  • Disallow/pbs/campaign/*/badge
  • Disallow/pbs/campaign/*/stats
  • Disallow/pbs/campaign/*/taborder
  • Disallow/pbs/campaign/*/largeImageHere
  • Disallow/pbs/campaign/*/graph
  • Disallow/pbs/campaign/*/timeline
  • Disallow/pbs/campaign/*/map
  • Disallow/pbs/campaign/*/thingedit
  • Disallow/pbs/campaign/*/new
  • Disallow/user/

User reviews (0)

  • No reviews yet.