<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/e2697a6760ab44459fc0758d9d9ccf0f&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e2697a6760ab44459fc0758d9d9ccf0f-5f5947232e83a323.gif</thumbnail_url><duration>450.688</duration><title>Outbound Infrastructure Guardrail System</title><description>This Loom explains how to build an outbound infrastructure guardrail to decide whether to allow, throttle, or pause sending based on domain health. It checks live DNS records for SPF, DMARC, and MX, converts results into pass or fail or marks items as not tested when selectors are not available, and uses a policies table in Google Sheets to set thresholds for spam complaint rate, bounce rate, and daily sending limits. The workflow combines infrastructure health and sending metrics to produce a final decision shown in Sheets, such as a critical status and pause when spam complaint rate for google.com is 0.35 and exceeds the configured warning level. A demo run is triggered manually and on an hourly schedule, and the test value is then changed from 0.35 to 0.05 to see how the decision updates.</description></oembed>