UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3293.0 Safari/537.36

Steps to reproduce the problem:
1. Open a page that redirects to a different domain
2. Try to look at the certificate for the server that served the redirect

What is the expected behavior?
It would be nice for this to be easily visible in the devtools or elsewhere. Other devtools tabs have a checkbox for "Preserve log", so it could make sense to add this to the Security tab. Or, in the Network log, when inspecting a particular request, click a tab or button to open the security information about the request's connection.

What went wrong?
As far as I can tell, the only way to do this at all is to use net-export to capture the PEM-encoded certificate.

If it's possible to break on redirects using the devtools I could not find it.

Did this work before? No 

Chrome version: 65.0.3293.0  Channel: canary
OS Version: OS X 10.13.2
Flash Version: 

If it's not clear, the use case here is for a login page that's served by a different domain, and I want to verify that I have configured the site properly.

This means that the possible workaround of "try to get a non-redirect response from the same site" is untenable, as it'll redirect everything until you show the right cookie.