Operations | Monitoring | ITSM | DevOps | Cloud

A DNS failure at Proofpoint broke email delivery for organizations around the world on August 14, 2026. Records for pphosted.com stopped resolving, so inbound and outbound mail routed through Proofpoint bounced or stalled for nearly four hours. StatusGator flagged the incident with an Early Warning Signal at 12:48 UTC, about an hour before Proofpoint acknowledged it publicly on its status page at 13:50 UTC. Here is what happened, who it hit, and how some teams kept mail moving.

Enterprise teams can now add a Syslog alert channel: every DNS Spy alert delivered as an RFC 5424 message over TLS (or TCP/UDP), formatted as JSON or ArcSight CEF, with syslog priorities mapped from real alert severity. All deliveries originate from one documented static IP, so getting through your collector's firewall is a single allowlist rule.

Sites often try to record information about visitors, which is why you’re often asked if you accept the use of cookies. When users want to remove the information collected, they clear the cache of their browsers. What many people don’t realize, though, is information is also stored in the domain name server (DNS) cache. This guide will explain in more detail what the cache is, how it’s used, and why it’s important to sometimes flush the DNS server cache.

GoDaddy manages more domains than any registrar on earth, so it has always been near the top of our provider integration list. There was just one problem: in May 2024, GoDaddy restricted its API to accounts holding ten or more domains — fifty for some endpoints. Overnight, certificate renewals broke, dynamic DNS scripts died, and every small business with one or two domains was locked out of automating anything.

Enterprise teams can now add a Webhook alert channel that POSTs every DNS Spy alert — DNS record changes, domain outages, security check failures, WHOIS updates, phishing look-alike detections — to any HTTPS endpoint as structured JSON. Requests are optionally HMAC-signed, every delivery is logged and retried, and a Send Test button verifies your integration end to end.

When we launched DNS provider sync with six providers, one name came up in nearly every "what about..." email: Amazon Route 53. That makes sense. Route 53 runs DNS for an enormous share of production infrastructure, and it does not support zone transfers — so until now, monitoring a Route 53 zone meant relying on autodiscovery's educated guesses. Today that gap closes.

When you add a domain to a DNS monitor, the first question is simple: which records should it watch? Until now there were two answers, and both had a catch. Autodiscovery probes hundreds of common names — www, mail, _dmarc, the usual suspects — and it catches most of what real zones contain. But if you named a record something unusual, no wordlist in the world is going to guess it.

Somewhere out there, a domain that looks almost exactly like yours may already be registered. Maybe it swaps one letter. Maybe it uses a Cyrillic character that is visually identical to a Latin one. Maybe it just adds the word "login" or "secure" to your brand. These lookalike domains are the raw material of phishing, and most companies have no idea how many exist for their brand until something goes wrong.

DNS TTL is one of those settings nobody thinks about until it bites them. Then they think about it a lot. This guide explains what DNS TTL is, how it works in plain language, and how to pick the right value for your records. By the end you will know what to set, when to change it, and why it matters when you migrate to a new server.