services / auth0

Auth0 (Okta CIC) IP ranges

Official Auth0 (Okta CIC) ranges from the vendor's publication, split by purpose: all, australia, canada, europe, japan, united-kingdom, united-states. The ranges below render live from the signed slash0 feed.

purposedirectionIPv4IPv6
auth0/allingress··
auth0/australiaingress··
auth0/canadaingress··
auth0/europeingress··
auth0/japaningress··
auth0/united-kingdomingress··
auth0/united-statesingress··

auth0/all

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_all" {
  service = "auth0"
  purpose = "all"
}

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

auth0/australia

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_australia" {
  service = "auth0"
  purpose = "australia"
}

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

auth0/canada

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_canada" {
  service = "auth0"
  purpose = "canada"
}

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

auth0/europe

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_europe" {
  service = "auth0"
  purpose = "europe"
}

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

auth0/japan

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_japan" {
  service = "auth0"
  purpose = "japan"
}

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

auth0/united-kingdom

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_united_kingdom" {
  service = "auth0"
  purpose = "united-kingdom"
}

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

auth0/united-states

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "auth0_united_states" {
  service = "auth0"
  purpose = "united-states"
}

resource "aws_security_group_rule" "auth0_united_states" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.auth0_united_states.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.auth0.all.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 Auth0 (Okta CIC)'s official publication: https://auth0.com/docs/secure/security-guidance/data-security/allowlist. Fetched sources:

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.