Message verification

Did that email really come from us?

We assess critical infrastructure, so we are a name worth impersonating. This page is how you check — without having to take our word for it.

The short version

We never ask for any of this.

If a message claiming to be from Wardhelm does any of the following, it is not from us. There are no exceptions, and no urgent situation that creates one.

⌧

Credentials

We never ask for a password, a one-time code, an MFA approval, or a password reset. Not for your systems, not for ours.
⎙

Unrequested attachments

We never send an attachment you did not ask for. No invoice, no report, no "updated proposal" arrives unannounced.
⇄

Changed bank details

We never change payment details by email. Banking instructions exist only inside a signed engagement document.
⚿

Remote access

We never ask you to install software, run a script, open a remote-support session, or disable a control.
⤫

Network activity before signature

No assessment activity of any kind happens on your network before a signed authorization and scope document exists. If someone claims work is already underway, it is not us.
⏱

Urgency

We do not create deadlines by email, and we never ask you to bypass your own process because something is time-critical.
Check it from outside

Check the message, not the signature block.

A logo, a job title and a signature can all be copied from one genuine email. Cryptographic alignment cannot. Our domain publishes a strict policy, and every one of these facts is checkable by you, from outside, without contacting us.

1 · The sending domain

Genuine mail arrives from an address at wardhelm.com. We do not send from look-alike domains, free mail providers, or any other company's domain.

2 · The signature on it

Our mail is DKIM-signed as wardhelm.com itself — not a subdomain. In your mail client's original-message view, look for dkim=pass header.d=wardhelm.com.

3 · The alignment

The same view should show dmarc=pass. If a message claims to be from @wardhelm.com and shows dmarc=fail, treat it as forged.

4 · Our published policy

Confirm the policy yourself from any machine:
dig +short TXT _dmarc.wardhelm.com
It publishes p=reject, so a receiver that enforces DMARC should refuse a forgery before it reaches you.

Two honest limits. First, p=reject protects our exact domain — it cannot stop someone registering a look-alike such as a capital-I or an rn for m, so read the sender domain character by character. Second, whether a forgery is actually refused depends on your own mail system enforcing DMARC; we publish the policy, your gateway decides to honour it.

If something deviates

Confirm out-of-band, then tell us.

Use a number or address you already hold for us from a previous signed document — never one supplied inside the message you are questioning. That single habit defeats almost every impersonation attempt, including ones far better built than the message that brought you here.

Report it to us

Forward the message with full headers to [email protected]. Headers matter more than the body — they are what identifies the real sender.

Do not reply to it

Replying confirms the mailbox is live and monitored, which is itself useful to an attacker. Forward it to us instead.

Keep it

Do not delete the original before forwarding. If it reached your inbox, your gateway's own logs are evidence worth preserving too.