# Basic CAA iodef support?

**URL:** <https://community.letsencrypt.org/t/basic-caa-iodef-support/199310>\
**Category:** Feature Requests\
**Created:** [May 31, 2023, 11:38pm UTC](https://community.letsencrypt.org/t/basic-caa-iodef-support/199310 "2023-05-31T23:38:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [May 31, 2023, 11:38pm UTC](https://community.letsencrypt.org/t/basic-caa-iodef-support/199310/1 "2023-05-31T23:38:18Z")

</div>

as now checkcaa function get accountURI and validationMethod, now it has everything strictly needed to tell a mailer send caa mail [timestamp] , [accountURI] requested certificate for [req.identifier] by [validationmothod] to iodef address. although this works, it will send a mail per each subdomain it requests and it can't differentiate initial caa check and recheck, so a lot of mail traffic is ensured

---

<div class="post-metadata">

**Author:** ![JamesLE](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jamesle/32/49364_2.png) [@JamesLE](https://community.letsencrypt.org/u/JamesLE)\
**Post date:** [June 1, 2023, 1:18am UTC](https://community.letsencrypt.org/t/basic-caa-iodef-support/199310/2 "2023-06-01T01:18:09Z")

</div>

Unfortunately, it’s not likely we’ll be able to add this in the near future. Sending email is unreliable, expensive, and requires a fairly large amount of care and feeding.

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [June 1, 2023, 2:08am UTC](https://community.letsencrypt.org/t/basic-caa-iodef-support/199310/3 "2023-06-01T02:08:49Z")

</div>

how about http version of rid? caa RFC have option to call http url for incident report on iodef [[RFC6546](https://www.rfc-editor.org/rfc/rfc6546)]  
not sure anyone actually using this though

---

<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:** [July 1, 2023, 2:09am UTC](https://community.letsencrypt.org/t/basic-caa-iodef-support/199310/4 "2023-07-01T02:09:15Z")

</div>

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