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

| A | 211.14.18.85 |
|---|---|
| MX | 10 mailforward.dnsv.jp |
| NS | ns-636.awsdns-15.net ns-304.awsdns-38.com ns-1522.awsdns-62.org ns-1877.awsdns-42.co.uk |
| TXT | v=spf1 ip4:52.199.227.187 -all |
| registered | 2016-03-14 |
|---|---|
| expires | 2027-03-31 |
| last changed | 2026-04-01 |
| owner | Ceres Inc. |
| nameservers | ns-1877.awsdns-42.co.uk ns-636.awsdns-15.net ns-1522.awsdns-62.org ns-304.awsdns-38.com |
| status | Active |
| valid | yes |
|---|---|
| issuer | Sectigo Limited |
| covers | *.ad-contents.jp, ad-contents.jp |
| protocol | TLSv1.2 |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 ip4:52.199.227.187 -all |
|---|---|
| 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-contents.jp.
Reference: /llms.txt.
IPv6. Does ad-contents.jp work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch ad-contents.jp. 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