Thanks for the M3AAWG reference—that is a great catch. You are spot on regarding the DMARC interaction. I used 'Safe/Secure' as simplified shorthand for the UI

Thanks for the M3AAWG reference—that is a great catch. You are spot on regarding the DMARC interaction. I used 'Safe/Secure' as simplified shorthand for the UI, but you're right that -all can sometimes pre-emptively kill connections before DMARC/DKIM evaluation, causing a loss of reporting data. I will update the UI labels to be more technical ('SoftFail' / 'HardFail') rather than editorializing them as 'Safe/Secure' to avoid misleading users. Love the idea of clickable nodes for the visualization drill-down. Adding that to the roadmap for the next sprint.