WP Mail SMTP replaces WordPress's outgoing mail transport with a real SMTP or API-based provider, entirely server-side — nothing it does is ever part of a page a visitor requests, so it has no public-facing footprint of its own at all. Its real relevance here is as supporting infrastructure: it's what makes other bridged plugins' notification emails — Contact Form 7, WPForms, Gravity Forms, Fluent Forms — actually get delivered reliably once their submission is bridged back to WordPress.
Fully Static
Everything — there is no public-facing feature to serve differently. Mail transport, the admin "send a test email" action, and the optional email activity log are all server-side or wp-admin-only.
None.
None needed — WP Mail SMTP declares no public routes of its own. It needs no bridge itself, but it's important supporting infrastructure for the plugins that do.
No special setup — detected automatically once active.
This has not been behaviorally validated against a live install, though its architecture (a phpmailer_init / wp_mail() transport override) is simple and stable enough that this is a low-stakes gap — the adapter declares no risks.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp