privacy policy<\/a>.<\/p>\n\nExternal service<\/h4>\n\n
This plugin connects to the DomainWarn API at https:\/\/api.domainwarn.com<\/code> (operated by Wigandt Technology,\nGermany). Without an API token that you create yourself, the plugin stays idle and contacts nothing. The API\naddress is configurable, DomainWarn can also be self-hosted.<\/p>\n\nIf you switch on \"Serve security.txt via DomainWarn\", the site fetches the file from\n https:\/\/domainwarn.com\/security-txt\/\u2026 when someone requests \/.well-known\/security.txt \u2013 at most once an hour \u2013 and\nserves it itself. Normal page views never contact DomainWarn: the address of the file is stored on the site and\nrefreshed by the scheduled run.<\/p>\n\n\n
\n- Install and activate the plugin.<\/li>\n
- Under Settings \u2192 DomainWarn, click \"Connect with DomainWarn\". You confirm in DomainWarn, and the token lands\nhere by itself. A free account is enough to start.<\/li>\n
- \"Add addresses\". Done.<\/li>\n<\/ol>\n\n
Prefer to do it by hand? Create a token in DomainWarn under Settings \u2192 API with write scope and paste it into the\ntoken field instead.<\/p>\n\n
For the heartbeat, WP-Cron must run \u2013 which is exactly what it checks.<\/p>\n\n\n
\nDo I need a paid account?<\/h3><\/dt>\nNo. The plugin is free and works with the free DomainWarn account. What is charged is the monitoring service, once\nmore domains or shorter check intervals are needed.<\/p><\/dd>\n
Is content of my site transmitted?<\/h3><\/dt>\nNo. Transmitted are addresses, versions, installed plugins and themes, sender address and mail server, and the\nmaintenance mode. No users, posts, comments or orders.<\/p><\/dd>\n
Does the plugin work with a self-hosted DomainWarn?<\/h3><\/dt>\nYes. The API address can be changed on the settings page.<\/p><\/dd>\n
Why does the plugin not serve MTA-STS as well?<\/h3><\/dt>\nThe MTA-STS policy belongs on a host of its own \u2013 mta-sts.example.com for example.com \u2013 with its own certificate; a\nrequest there never reaches WordPress, and RFC 8461 forbids following redirects when a mail server fetches the\npolicy. DomainWarn serves it once a CNAME points to it. The plugin shows that record and the TXT record to copy, and\nlinks to the page in DomainWarn that sets both with one click.<\/p><\/dd>\n
Why does DomainWarn open an incident although my site is up?<\/h3><\/dt>\nBecause the heartbeat stopped. Then WP-Cron has stalled: the site still answers, but it sends no mail and processes\nnothing.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.3.2<\/h4>\n\n\n- security.txt is served by the site itself (status 200, no redirect), kept for an hour, with the last good copy\nwhile DomainWarn cannot be reached. \"Check security.txt\" recognises this and reports an outdated cached copy.<\/li>\n
- Two installations under one domain (for example kunde.de and blog.kunde.de) each report their own inside view and\nping their own heartbeat.<\/li>\n
- Multisite: only the main site reports the whole network, and only network admins manage the settings there; a\nsub-site reports just itself. Networks with more than 100 sites are reported in full.<\/li>\n
- \"Test connection\" and the other buttons on the settings page save the form first instead of dropping a freshly\nentered token.<\/li>\n
- Opening the settings page in a second tab no longer breaks a connection in progress.<\/li>\n
- The dashboard widget keeps the figures of the first run.<\/li>\n
- Sites under internationalised endings such as .\u0440\u0444 are recognised.<\/li>\n
- Removed the switch \"Add the addresses of this site to DomainWarn\", which had no effect.<\/li>\n<\/ul>\n\n
1.3.1<\/h4>\n\n\n- Heartbeat: after a 404 the scheduled run sets the heartbeat up again instead of pinging into the void; changing the\ntoken or slug clears the remembered address.<\/li>\n
- \"Report now\" and
wp domainwarn report<\/code> show a notice instead of a fatal error when DomainWarn cannot be reached.<\/li>\n- Network activation schedules the run on every site of the network.<\/li>\n
- Connecting works when the site and the admin run on different hosts.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- New: the \"DomainWarn\" dashboard widget shows, per domain of the site, its state, availability over 30 days, the\nresponse time of the last 7 days, when certificate and domain expire and the open incidents, with a link to the\ndomain in DomainWarn. Only for administrators.<\/li>\n
- The figures come from the scheduled run, at most once an hour (\"Report now\" and
wp domainwarn report<\/code> refresh\nthem right away). Opening the dashboard never contacts DomainWarn.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n\n- New: \"Serve security.txt via DomainWarn\" (off by default). The site answers \/.well-known\/security.txt with a\nredirect to the file DomainWarn hosts \u2013 only at the domain itself or www, only to DomainWarn, never over an\nexisting security.txt.<\/li>\n
- New: \"Check security.txt\" fetches the address like a researcher and shows whether the redirect arrives, whether a\nvalid file waits at the target and whether a file or another plugin answers as well.<\/li>\n
- New: \"Hosted by DomainWarn\" shows the state of security.txt, MTA-STS and the BIMI logo with the records to copy.<\/li>\n
- Domain names with umlauts are added in the form DomainWarn uses (Punycode) instead of being skipped.<\/li>\n
- Requires PHP 8.2. The plugin already relied on PHP 8.2 while declaring 8.1, so on PHP 8.1 it failed with a fatal\nerror. On an older PHP it now stays inactive and says so in the admin area.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- \"Connect with DomainWarn\" sets the connection up with one click \u2013 no token to copy.<\/li>\n
- \"Assign to client\" is a list of your clients in DomainWarn instead of a free text field.<\/li>\n
- The organization slug and the API address moved under \"Advanced\".<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- The scheduled run is now really scheduled: on activation the 15-minute interval was not known yet, so no\nheartbeat was ever set up.<\/li>\n
- Corrected links and contributor in this readme.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release: add addresses to monitoring, report the inside view, heartbeat against a stalled WP-Cron, settings\npage and WP-CLI commands.<\/li>\n<\/ul>","raw_excerpt":"Monitors availability, certificate, DNS and email of your site \u2013 and reports what is invisible from outside: outdated plugins, a stalled WP-Cron.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/374856","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=374856"}],"author":[{"embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/wigandt"}],"wp:attachment":[{"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=374856"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=374856"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=374856"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=374856"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=374856"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/af.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=374856"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}