Apex domain monitoring: watch the zone apex before the bare name goes dark
Apex domain monitoring is how you notice the bare name went empty—or someone pasted a raw CNAME at the zone apex—before the homepage, CDN, and client tickets all light up. CrowWake’s check is a public A/AAAA + CNAME-at-apex pulse, not a full zone audit.
What apex domain monitoring means here
Operators searching for apex domain, zone apex, or apex DNS usually want two answers: what is the bare name, and is it still resolving the way they set it? CrowWake’s monitoring answer is the second: live A and AAAA at example.com, plus whether a CNAME is sitting on that same name. It sits beside DNS A monitoring, website HTTPS, and SSL so “the apex vanished” shows up in the same flock as “the site is down.”
What CrowWake checks
Public DNS for the bare domain: A and AAAA addresses, and whether a CNAME appears at the apex. Missing address records → warn. A CNAME at the apex → warn so you notice provider flattening vs a mis-paste next to SOA/NS. Healthy A/AAAA with no raw apex CNAME → ok, with a short summary of what resolved. The free apex checker uses the same posture with no login—the same signal the hourly flock uses. CrowWake does not inventory every subdomain; it watches the zone apex row clients hit when they type the brand without www.
Monitoring vs “what is an apex domain”
The apex domain guide explains zone apex, bare domain, and apex record in plain English. The CNAME at apex guide covers ALIAS, ANAME, and flattening when a CDN asks you to “CNAME the domain.” Monitoring is the repeat job: catch a silent @ wipe after a panel edit, a registrar lock mishap, or an accidental raw CNAME beside SOA/NS. All of them use the same free apex checker; CrowWake just repeats the pulse every hour. DNS A monitoring is the sibling check focused on “does this hostname still have IPv4?”
What “good enough” looks like
Public DNS for example.com answers with the IPs (or flattened addresses) you expect. www is a separate choice. If you use Cloudflare/Route53-style apex aliasing, resolvers should still see A/AAAA—CrowWake cares about what the internet sees, not the proprietary record type in your panel. Intentional parked or mail-only apices without web A/AAAA are fine when you know that is the design.
Quick triage when the apex goes yellow
1) Re-run the free apex checker and note A/AAAA vs CNAME-at-apex. 2) Confirm you edited host @ (blank), not only www. 3) If a raw CNAME is present and your host does not flatten, remove it and use ALIAS/ANAME/flattening or real A/AAAA—see the CNAME at apex guide. 4) Confirm HTTPS still answers after DNS settles (website HTTPS / uptime checker). 5) Add the domain so CrowWake crows on the next silent wipe instead of waiting for a client “the site is gone” email.
If CrowWake crows
Treat the pulse as source of truth for “what public DNS says about the bare name,” not a full zone transfer. Use the apex domain guide for definitions, the CNAME at apex guide for flattening conflicts, re-run the free apex checker after a fix, then keep watching. Pair with DNS monitoring and website monitoring so resolve vs HTTPS stay separate roosters.
Watch this on CrowWake
Add the domain, leave the boxes checked, and the flock will crow when this drifts.
Or try the free apex domain monitoring / zone apex checker with no login.
Related: what is an apex / zone apex, CNAME at apex, DNS monitoring, and uptime monitoring (resolve first, then HTTPS).