13 controls
0 frameworks share controls with it
United States (federal)
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
No measured overlap with another framework in the corpus.
Every control
| Code | Control | Also in |
316.5 | 16 CFR 316.5 Do not charge for, or add hurdles to, opting out | 0 |
7704a1 | s 7704(a)(1) Do not use materially false or misleading header information | 0 |
7704a2 | s 7704(a)(2) Do not use deceptive subject lines | 0 |
7704a3 | s 7704(a)(3) and (a)(5)(A)(ii) Provide a working, conspicuous opt-out mechanism that stays live for 30 days | 0 |
7704a4 | s 7704(a)(4) Honour opt-outs within 10 business days and never sell or transfer opted-out addresses | 0 |
7704a5i | s 7704(a)(5)(A)(i) Identify the message clearly and conspicuously as an advertisement | 0 |
7704a5iii | s 7704(a)(5)(A)(iii) Include the sender's valid physical postal address | 0 |
7704b | s 7704(b) Do not harvest addresses, use dictionary attacks, script account creation or relay without authorisation | 0 |
7704d | s 7704(d) and 16 CFR 316.4 Label sexually oriented commercial email | 0 |
7705 | s 7705 Businesses promoted in email: take reasonable action against messages with false header information | 0 |
enforcement | Enforcement, penalties and preemption | 0 |
scope | What is covered: commercial electronic mail and its sender | 0 |
status | Status and currency | 0 |
Tell me when United States CAN-SPAM Act of 2003 and FTC CAN-SPAM Rule (16 CFR Part 316) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What this page is
A control-level reference for United States CAN-SPAM Act of 2003 and FTC CAN-SPAM Rule (16 CFR Part 316), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition