# Policy forbids issuing for name: www.adp.co.il **URL:** \ **Category:** Issuance Policy\ **Created:** [February 28, 2017, 5:34pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863 "2017-02-28T17:34:21Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![fxposter](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fxposter/32/9972_2.png) [@fxposter](https://community.letsencrypt.org/u/fxposter)\ **Post date:** [February 28, 2017, 5:34pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/1 "2017-02-28T17:34:21Z")
Hello. I’ve found a couple of questions with the same name and most of them ended with manually whitelisting the domains by LE team. And so, I have these questions: 1. If I get errors like `acme: Error 400 - urn:acme:error:rejectedIdentifier - Policy forbids issuing for name` - are there any ways to find out what are the reasons behind it? 2. Is this error should be treated as permanent (ie: it’s useless to just retry in some amount of time if we get such error)? 3. Is it possible to whitelist at least the domain in title ([www.adp.co.il](http://www.adp.co.il)) for now? 4. Is there any automated way of dealing with such domains (cause I believe we would have a bunch of them)? Thanks! ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [February 28, 2017, 5:42pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/2 "2017-02-28T17:42:52Z")
Hi @fxposter, > [@fxposter](#): > > If I get errors like acme: Error 400 - urn:acme:error:rejectedIdentifier - Policy forbids issuing for name - are there any ways to find out what are the reasons behind it? There's not much to know beyond what's in the error text in this case. > [@fxposter](#): > > Is this error should be treated as permanent (ie: it's useless to just retry in some amount of time if we get such error)? Yes - retrying won't help without manual intervention from Let's Encrypt staff & a deploy cycle. > [@fxposter](#): > > Is it possible to whitelist at least the domain in title (www.adp.co.il) for now? I can start the process to adjust the policy for this name.[quote="fxposter, post:1, topic:28863"] Is there any automated way of dealing with such domains (cause I believe we would have a bunch of them)? [/quote] There isn't any automated way to deal with this. Apologies. ---
**Author:** ![fxposter](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fxposter/32/9972_2.png) [@fxposter](https://community.letsencrypt.org/u/fxposter)\ **Post date:** [February 28, 2017, 5:48pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/3 "2017-02-28T17:48:46Z")
Hi! > [@cpu](#): > > There's not much to know beyond what's in the error text in this case. Are there any list of such policies anywhere? > [@cpu](#): > > I can start the process to adjust the policy for this name. Please, do. Thanks! Would it be possible if we gather all domains that give such errors to us and post it here, so that you can bulk-whitelist them? ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [February 28, 2017, 5:50pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/4 "2017-02-28T17:50:08Z")
> [@fxposter](#): > > Are there any list of such policies anywhere? Unfortunately the list of domains isn't publicly available. > [@fxposter](#): > > Would it be possible if we gather all domains that give such errors to us and post it here, so that you can bulk-whitelist them? Yes, that would be great. I'll have to verify each independently and submit policy adjustments. ---
**Author:** ![fxposter](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fxposter/32/9972_2.png) [@fxposter](https://community.letsencrypt.org/u/fxposter)\ **Post date:** [February 28, 2017, 5:51pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/5 "2017-02-28T17:51:14Z")
> [@cpu](#): > > Yes, that would be great. I'll have to verify each independently and submit policy adjustments. Thank you. Will get back later this week. ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [February 28, 2017, 9:32pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/6 "2017-02-28T21:32:38Z")
By the way, I think the reason this may originally have been blacklisted is the similarity with the ADP company in the U.S. [https://en.wikipedia.org/wiki/Automatic\_Data\_Processing](https://en.wikipedia.org/wiki/Automatic_Data_Processing), which I believe is the biggest payroll services and employee benefits company. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [March 7, 2017, 3:37pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/7 "2017-03-07T15:37:23Z")
Hi again @fxposter, You should be able to issue for `adp.co.il` domains now. Please let me know if you’re still encountering a policy error. Thanks! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 6, 2017, 3:37pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-www-adp-co-il/28863/8 "2017-04-06T15:37:49Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.