It’s a little unfair to post about this as a support question and a bad review in the next day, @bandsaw12
https://wordpress.org/support/topic/age-header-missing/
And the error is correct. Nginx dropping support for age headers is something that happened, but it’s still an HTTP standard. The fact that Nginx is being weird doesn’t invalidate the check.
That said, the plugin will still work. The checker doesn’t work correctly for your site, but the cache-flush is not reliant on that.
After trying to figure out what headers the plugin wanted to see for about 5 hours without any documentation as to what you were expecting to see from the NGINX headers, I see the this as appropriate. I will concede maybe it should have had two stars, but then again, I never got it working. Documentation says it works with Varnish and NGINX – not the combination of both required (just that the PURGE request has to be honored). It would not be normal for NGINX to respond with Varnish is it’s header. Improve the documentation to tell users ‘exactly” what your plug in is looking for in the headers for proper operation and I will give this another go.
