Skip to content
Trustlayer Technologies Ltd

01 Trustlayer Technologies Ltd · United Kingdom

Business email
people can trust.

Every email your organisation sends makes a claim: this came from us, and this is who we are. Trustlayer builds the software that makes both halves of that claim true — the records that prove where mail came from, and the signature that says who sent it.

Two products · One company · Registered in England and Wales

Layer 01 — identity
Who the email is from

One signature template across the organisation, filled from your directory. Footersly.

Layer 02 — authentication
Proof it really is

SPF, DKIM, DMARC and the rest, checked the way a receiving server reads them. MailAuthInspector.

Layer 03 — the result
Mail that lands, and looks it

Delivered, consistent, and defensible — to the inbox and to an auditor.

02
Products in the group, both live
6
Mail standards checked end to end
UK
Company, hosting and data residency
0
Third-party trackers on this site

02 The group

Two products, one problem, approached from both ends.

Trustlayer Technologies is the parent company. Each product is run as its own service with its own customers, its own release cycle and its own domain — and both answer to the same company, the same security practice and the same privacy notice.

Footersly

LIVE
footersly.com

Email signatures, centrally held

Footersly puts every signature, disclaimer and campaign banner in your organisation under one set of templates - applied from Microsoft 365, filled from your directory, and changed without anybody editing Outlook.

01 One template, every mailbox

Build a signature once and apply it across the tenant. Per-user fields - name, title, team, phone, photo - fill themselves from Microsoft Entra ID, so a new starter has a correct signature on their first morning.

02 Disclaimers that stay intact

Legal text is held separately from the design and previewed against the live signature before it goes out, so a brand refresh cannot quietly drop the wording your lawyers approved.

03 Campaign banners with an end date

Run a banner under the signature for a launch or an event, scoped to the teams it applies to, with a start and an end date so nothing is still advertising a conference that happened last spring.

04 Directory sync and sync groups

Connect the tenant once. Sync groups decide who gets which template, and the user list the templates apply to is the one that already comes through from the directory.

MailAuthInspector

LIVE
mailauthinspector.online

SPF, DKIM, DMARC - checked and watched

MailAuthInspector reads the DNS records that decide whether your mail is trusted - SPF, DKIM, DMARC, BIMI, MTA-STS - tells you what is wrong in plain words, and keeps watching so it stays right.

01 Every record, one lookup

SPF, DKIM, DMARC, BIMI, MTA-STS and TLS-RPT resolved live from authoritative DNS, with the raw answer kept alongside the verdict so you can see what was returned rather than take our word for it.

02 SPF, evaluated the way a receiver does

Includes are followed and counted. The ten-lookup limit, void lookups, a stray +all, a record split across two TXT entries - the failures that pass a glance and fail in production are named explicitly.

03 DMARC you can actually move

Read the policy you have, see what p=quarantine then p=reject would do to real mail first, and work through alignment one sending source at a time.

04 Aggregate reports, read for you

DMARC XML from the receivers is parsed into sending sources, volumes and pass rates, so a report nobody opens becomes a list of senders to fix or authorise.

03 How we work

Four things we will not trade away.

Both products sit in the path of somebody's business email. That is a serious place to be, and it sets how we build.

01 / Plain words
Say what is wrong, not that something is

A red cross is not a finding. Our tools name the record, the line in it and what to change, because the person reading it has to fix it today.

02 / Least data
We hold as little as the job allows

We ask for the directory fields a signature needs and the DNS records a check needs. We do not read your mail, and nothing we build needs to.

03 / UK by default
A UK company, with UK hosting

Registered in England and Wales and run under the UK GDPR, with customer data held in UK or EU regions and every sub-processor listed in public.

04 / Auditable
Who changed what, kept on the record

Administrative change is logged with the person behind it — including a provider's delegate who holds no account in your tenant.

04 Who it is for

Built for the people who get the ticket.

Email signatures and mail authentication land on the same two or three desks in most organisations. These are those desks.

IT and infrastructure
In-house teams

You own the tenant and the DNS zone, and you would rather not touch either at 7am because marketing changed a logo. Templates and records become something you set once and can prove.

Managed service providers
One screen per portfolio

Dozens of tenants, hundreds of domains, and a client who wants to know why their invoices go to junk. Both products group by organisation and let a delegate work without an account in the client's tenant.

Marketing, legal and compliance
The people with the requirement

The brand has to be right and the disclaimer has to stay intact. Both are held as their own thing, previewed before release, and changed without a message going round asking everyone to update Outlook.

Start where it hurts most.

Check a domain's authentication in a minute with no account, or put a trial signature across one team and see it land. If you would rather ask a person first, that works too.