# Policy forbids issuing for name - beta.rbc.org

**URL:** <https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291>\
**Category:** Issuance Policy\
**Created:** [May 27, 2016, 1:32pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291 "2016-05-27T13:32:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![t0mm0r](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@t0mm0r](https://community.letsencrypt.org/u/t0mm0r)\
**Post date:** [May 27, 2016, 1:32pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291/1 "2016-05-27T13:32:38Z")

</div>

I am trying to request a certificate for my organization that owns the domain name [rbc.org](http://rbc.org). We host several beta versions of our sites using sub-domains of [beta.rbc.org](http://beta.rbc.org) but everytime I try to request anything for [rbc.org](http://rbc.org) it gives me the following error: `Error: urn:acme:error:malformed :: The request message was malformed :: Error creating new authz :: Policy forbids issuing for name` We also own the domain [ourdailybread.org](http://ourdailybread.org) and I was able to request a certificate for [beta.ourdailybread.org](http://beta.ourdailybread.org) without any issues. Below is the log output:

````auto
    typ=messages.IDENTIFIER_FQDN, value=domain), new_authzr_uri)
  File "/home/twilson/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 197, in request_challenges
    new_authz)
  File "/home/twilson/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 652, in post
    return self._check_response(response, content_type=content_type)
  File "/home/twilson/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 568, in _check_response
    raise messages.Error.from_json(jobj)
Error: urn:acme:error:malformed :: The request message was malformed :: Error creating new authz :: Policy forbids issuing for name```
````

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [May 27, 2016, 1:46pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291/2 "2016-05-27T13:46:23Z")

</div>

RBC sounds like a bank, and the first thing that comes up when I Google RBC is the Royal Bank of Canada. I’d therefore guess that rbc.\* is on the “high risk domains list”, prohibiting issuance. Hopefully someone can chime in with a more definitive answer, and if there’s a way to work around it.

---

<div class="post-metadata">

**Author:** ![t0mm0r](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@t0mm0r](https://community.letsencrypt.org/u/t0mm0r)\
**Post date:** [May 27, 2016, 1:50pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291/3 "2016-05-27T13:50:37Z")

</div>

Yeah I was kind of wondering if that was it.

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [May 27, 2016, 1:52pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291/4 "2016-05-27T13:52:39Z")

</div>

Your domain matches a list of high-profile phishing targets, most likely due to it’s similarity to [rbc.com](http://rbc.com) (Royal Bank of Canada). CAs are obliged to maintain such a list and use additional verification mechanisms when verifying domain ownership for such domains. That usually comes down to manual verification, which wouldn’t work in the case of Let’s Encrypt due to its automated nature, so domains on this list are essentially prohibited from requesting certificates.

The list does [occasionally get amended based on user feedback](https://community.letsencrypt.org/t/domain-blacklisted/10945/3?u=pfg), but I’m not sure if that would be appropriate here.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 26, 2016, 1:52pm UTC](https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-beta-rbc-org/16291/5 "2016-06-26T13:52:44Z")

</div>

Closed on June 26, 2016, 1:52pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.