DocuSign IP ranges

Official DocuSign ranges from the vendor's publication, split by purpose: connect-webhooks, email. The ranges below render live from the signed slash0 feed.

The feed classifies this service as mixed: not every purpose runs on vendor-dedicated infrastructure. Review a purpose before treating its ranges as exclusively DocuSign.

purpose	direction	IPv4	IPv6
`docusign/connect-webhooks`	ingress	·	·
`docusign/email`	ingress	·	·

docusign/connect-webhooks

Direction: ingress. Ranges DocuSign connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.

loading ranges from the feed…

Terraform

data "ipranges_ingress" "docusign_connect_webhooks" {
  service = "docusign"
  purpose = "connect-webhooks"
}

resource "aws_security_group_rule" "docusign_connect_webhooks" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.docusign_connect_webhooks.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

docusign/email

Direction: ingress. Ranges DocuSign connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.

loading ranges from the feed…

Terraform

data "ipranges_ingress" "docusign_email" {
  service = "docusign"
  purpose = "email"
}

resource "aws_security_group_rule" "docusign_email" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.docusign_email.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

keep rules current automatically

Terraform data sources refresh only when you run an apply. The hosted tier publishes the same data via AWS managed prefix lists (slash0.docusign.connect-webhooks.v4 and so on), shared into your account via AWS RAM: rules reference one pl-… id and update within a minute of a vendor change, with removals held through a 72 hour grace window. Request early access or read how it works.

provenance

Ranges come from DocuSign's official publication: https://www.docusign.com/trust/security/esignature. Fetched sources:

https://www.docusign.com/trust/ip-ranges.json

Every publish is signed (ECDSA P-256 over the feed index, each service document hash-chained to it) and every range change is recorded in the changelog. Verification steps: security. Provider setup: quickstart.