PlungeAI · Trust Center

Network security

Coming soon

How traffic to and between our services is protected.
2 in place · 2 coming soon

Firewall and WAF

Coming soon

Not documented yet. Will describe the firewall rules we set at the edge.

This will describe the web application firewall rules we set on Cloudflare in front of the services.

Spoofing protection (SPF, DKIM, DMARC)

Coming soon

Not documented yet. Will describe the SPF, DKIM and DMARC records for plungeai.com.

This will describe the SPF, DKIM and DMARC records that protect mail sent from plungeai.com. The live checks on this page read the SPF and DMARC records as they stand.

Service-to-service authentication

In place

Calls between our services run over Service Bindings or are signed with replay protection.

Calls between our own services run over Cloudflare Service Bindings, or are authenticated with signed requests that carry replay protection.

Source: Security, Infrastructure and encryption

TLS

In place

All traffic to the services uses TLS, and plain HTTP is redirected to HTTPS.

Traffic to the services is encrypted with TLS. Plain HTTP requests are redirected to HTTPS.

Source: Security, Infrastructure and encryption