Often different organizations have the same questions around our Dynamic DMARC offering so we’ve grouped them all together to address some key concerns...

How does Dynamic DMARC adapt to load? Does it auto-scale?

Dynamic DMARC clusters, including Dynamic SPF and DKIM, are maintained in Google Cloud Platform (GCP) and separated from our main infrastructure which is hosted in IBM Cloud. We have auto-scaling redundant clusters serving SPF, DKIM and DMARC with separate clusters for SPF and DKIM/DMARC so in the unlikely event that one were to fail, DMARC would still pass

How is Dynamic DMARC protected against DoS (Denial of Service) attacks?

Red Sift follows the best practice recommended by GCP to protect and mitigate against DoS and DDoS attacks.

How does Red Sift minimize the impact of any Dynamic DMARC outages?

We have built failover and geo-redundancy into the system to ensure the likelihood of all our clusters being down at the same time is extremely low.

What failover systems are in place in the unlikely event of a Dynamic DMARC outage?

We have a 24/7 rota in place to address any unlikely outages. To check our uptime over the last few months follow the links below:

Dynamic DMARC SLA: https://synthetics.newrelic.com/report/KS2nS?view=monthly-sla-report

Dynamic SPF SLA: https://synthetics.newrelic.com/report/zXuT7?view=monthly-sla-report

To give you an example, we have a large Telco relying on our Dynamic SPF service to process millions of SPF requests for them daily. They have telco grade infrastructure across the world that authenticates via this service and our approach continues to provide an optimal solution even at this scale.

If you are experiencing any issues please contact us using the button below

Did this answer your question?