Registered 9 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 64 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 104.20.47.80 172.66.148.140 |
|---|---|
| AAAA | 2606:4700:10::ac42:948c 2606:4700:10::6814:2f50 |
| NS | anna.ns.cloudflare.com anuj.ns.cloudflare.com |
| TXT | google-site-verification=RiwDJJmXVh8G1-nJeAx_CBtSrd7mTEWS9jI9iUkkDxA |
| registrar | RegistryGate GmbH |
|---|---|
| registered | 2017-05-03 |
| expires | 2027-05-03 |
| last changed | 2025-11-22 |
| owner | c/o whoisproxy.com |
| nameservers | anna.ns.cloudflare.com anuj.ns.cloudflare.com |
| status | client transfer prohibited |
| valid | yes |
|---|---|
| issuer | Google Trust Services |
| covers | ad-delivery.net, *.ad-delivery.net |
| protocol | TLSv1.3 |
Domain is not signed with DNSSEC
| SPF | none |
|---|---|
| DMARC | none |
| DKIM | none of 1 common selectors |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on ad-delivery.net.
Reference: /llms.txt.
IPv6. Does ad-delivery.net work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch ad-delivery.net. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days