CYBERREFLEX / FIELD NOTES

Know what changed.
Know what to do next.

Short, practical guides to the public signals that can affect your website and email. Learn what a check means, what it cannot prove, and how to respond.

01 / GUIDES

Start with the issue you see.

01 / DNS CHANGES

DNS change monitoring: know what changed before accepting it

A practical guide to important DNS changes, how to review them, and why one unexpected record should not be mistaken for a confirmed attack.

02 / TLS CERTIFICATES

TLS certificate monitoring: avoid the expiry surprise

Understand certificate expiry, name mismatch, and the simple checks that keep an HTTPS website accessible.

03 / EMAIL SECURITY

SPF and DMARC: a practical starting point for domain email security

Learn what SPF and DMARC publish in DNS, what they do not guarantee, and how to review changes before they affect legitimate mail.

04 / DOMAIN VERIFICATION

Why domain control verification comes before monitoring

See how DNS TXT and HTTPS challenge proofs show technical control of a domain before Guardian starts monitoring it.

05 / WEBSITE AVAILABILITY

Website availability monitoring: make an outage actionable

How external HTTPS checks, repeated failures, and recovery checks turn a website outage into a useful response workflow.

06 / HOW GUARDIAN WORKS

How Guardian verifies a domain and monitors public signals

A transparent look at domain control proof, scheduled checks, evidence, and the limits of CyberReflex Guardian monitoring.

07 / DNS SECURITY

DNS security for a business domain: the records that matter

A practical map of A, AAAA, NS, MX, and CAA records, what a change can affect, and how to review it without guessing.

08 / MX RECORD CHANGES

MX record changed unexpectedly: what to check first

A calm response to an unexpected MX record: verify the planned mail route, inspect provider settings, and test delivery before changing DNS.

09 / HTTP SECURITY HEADERS

HTTP security headers: what to check before changing them

Understand CSP, HSTS, and X-Content-Type-Options, their operational risks, and what a public header check can actually prove.

10 / SECURITY GLOSSARY

Cybersecurity terms for website owners, in plain language

Plain-language definitions of DNS, TLS, SPF, DMARC, incidents, baselines, and other terms used when monitoring a business domain.

02 / PLAIN LANGUAGE

A few useful terms.

Enough to understand the alert without needing a security dictionary.

DNS baseline
A previously observed set of DNS values used to notice a later change. It is a reference point, not a claim that the values are safe.
TLS certificate
A certificate that helps a browser verify the identity of the HTTPS site it reached.
SPF
A DNS policy describing authorized senders for an email envelope domain.
DMARC
An email policy that connects SPF or DKIM results to the visible From domain.
Incident
A confirmed issue recorded with observations, a response path, and a later recovery check.

Explore the full cybersecurity glossary ↗