KOVA OSKOVA OS · SHIELD
Check the public records behind your business email free. Shield reviews approved senders and prepares authentication changes for your written approval.
$750 one-time · 1 business domain · up to 3 approved sending services · written approval before changes
Reads public settings only. No mailbox password or login. It cannot identify every service that sends for you.
Is Shield a fit? For a business using its own email domain that needs help reviewing authentication across its mail platform and sending tools.
Shield does not investigate compromised accounts, stop lookalike domains or fake display names, build bulk cold-email infrastructure, or guarantee inbox placement. Verify payment requests through a separate trusted channel.
Ask whether Shield fits →WHAT THE CHECK SEES AND SETUP VERIFIES
Your IT provider retains ownership and access. Shield prepares the agreed authentication work and records the checks alongside them.
Why $750, and who does what →View the sample Shield Record →APPROVE THE CHANGE. KEEP THE RECORD.
SYNTHETIC SAMPLE · REHEARSAL ONLY
See the handoff format: checks, approved changes, and open items. Fictional sample—not a customer result or live verification.
Inspect the full sample →AUDIT: SPF v=spf1 include:_spf.google.com ~all | DMARC p=noneSENDERS: [01] Google Workspace [02] QuickBooks Online [03] HubSpot CRMPLANNED CHANGE: dkim._domainkey.domain.com | _dmarc.domain.comEXAMPLE RESULT: Workspace (dkim=pass spf=pass) | QuickBooks (aligned)NOTES: New marketing platform onboarding protocol documentedEXAMPLE: Prepared record · not delivered to a client · administrative owner to be confirmedPre-implementation review recording published SPF, DKIM, and DMARC configurations before any changes occur.
AUDIT: SPF v=spf1 include:_spf.google.com ~all | DMARC p=noneRepresentative scenario showing how a typical multi-sender environment can be structured: an initial observation finds a monitoring-only policy (p=none) alongside billing mail that needs alignment review. During a staged setup after access and written approval, approved sending sources can be mapped, exact changes reviewed before publication, and the policy advanced only when the agreed checks support it. Actual results and open items are then recorded in the client handoff.
DATED INTERNAL IMPLEMENTATION EVIDENCE
Historical public-record evidence from the date above. It does not prove every sending service works correctly, guarantee delivery, or show today’s settings.
Kova Shield is founder-led. Al Cirton is the named setup owner. Meet Al →
THE OFFER AND STRAIGHT ANSWERS
KOVA SHIELD SETUP · ONE-TIME ENGAGEMENT
$750 one-time
You get a sender review, a plan for your approval, checks after approved changes, and a dated record of results and open items.
Ongoing review is separate and optional. When your business adds another sending service, its authentication needs to be checked too. See setup scope and optional review →
Your setup owner: Al Cirton. Your IT provider keeps ownership and access. Changes require your written approval.
Inspect the synthetic sample record →It shows the handoff format, not a customer result or live verification. Results and open items are recorded for the agreed work.
Clear limits on the public check, the setup work, and what still belongs with your IT provider.
Read how Shield works →A sending service is a tool or platform sending messages using your domain, such as Microsoft 365, a CRM or invoicing service—not each employee mailbox. We confirm the included services before work.
No. SPF, DKIM, and DMARC can help participating mail systems handle messages that pretend to come from your exact domain. They do not stop lookalike domains, compromised accounts, fake display names, or social engineering. Keep payment verification separate from email.
Your IT provider retains ownership and access. Shield handles the agreed sender inventory, proposed authentication changes, checks and record alongside them. Changes require written approval.
No. Shield checks authentication for the included sending services. Inbox placement also depends on reputation, content, recipient behavior, filtering, and sending practices.
An enforced DMARC policy can tell participating recipient systems to quarantine or reject mail that fails alignment. This reduces direct-domain spoofing risk. It does not stop lookalike domains, compromised accounts, or fake display names.
Estimated 3–7 business days after required access and written approvals. DNS propagation, third-party sender verification and observation may extend timing; this is not a promise of full DMARC enforcement in that window.
No passwords are needed for the initial public check. For implementation, your DNS administrator or IT provider can publish approved updates directly, or use a least-privileged access method that fits your process. Kova Shield should never require your mailbox password.
See what is published for your domain. If you need help deciding what follows, ask about a scoped review.
Baseline review scope and price are confirmed before work. An inquiry takes no payment and authorizes no DNS change or subscription.