Search and citation guide
There is one box in the header and it answers two kinds of question. Type a citation and it goes straight there; type anything else and it searches the text. You do not have to tell it which you meant — it reads what you wrote.
Both halves can also ask about the past. A citation can name a release point and land on the provision as it stood then, and a search can name one too — though only through the URL for now, and with a limit worth reading first. See searching at a release point.
Going to a citation
Each of these forms works, and each is followed by the official identifier it resolves to. Select any example to try it.
-
The standard citation
11 U.S.C. § 523goes to/us/usc/t11/s523Title, U.S.C., section. The section symbol is optional, so is every period, and so is the spacing: 11 usc 523 and 11 U. S. C. 523 are the same citation.
-
Down to a subdivision
11 U.S.C. § 523(a)(1)(B)(ii)goes to/us/usc/t11/s523/a/1/B/iiParentheses become path segments, as deep as you write them. Case is kept: (B) is not (b), because the official identifiers distinguish the two.
-
A section number that is not a number
16 usc 45f(c)(5)goes to/us/usc/t16/s45f/c/5Section numbers carry letters — 45f, 1a, 78j-1 — and are matched as written rather than as an integer.
-
A hyphenated section number
42 USC 2000e-2goes to/us/usc/t42/s2000e-2Type the hyphen your keyboard has. The official text writes these with an en dash (45a–1, U+2013), so both spellings are tried and whichever exists is what you land on.
-
The inverted form
section 523 of title 11goes to/us/usc/t11/s523The way a statute refers to itself in prose. Sec., §, and a subdivision all work here too: Sec. 523(a) of Title 11.
-
Title last
Section 14123(a)(2), 49 U.S.C.goes to/us/usc/t49/s14123/a/2The abbreviated inverted form used in the Office of the Law Revision Counsel's own notes.
-
Title and section, nothing else
11/523goes to/us/usc/t11/s523The fastest thing to type. Subdivisions follow as slashes: 11/523/a/1.
-
The identifier itself
/us/usc/t16/s45f/c/5goes to/us/usc/t16/s45f/c/5The official USLM @identifier, pasted straight in — which is also this site's URL scheme, so a URL from anywhere on the site works in the box. Fragments of one do too: t16/s45f.
-
A chapter or other level
11 usc ch. 5goes to/us/usc/t11/ch5Chapters, subchapters, parts, subparts and subtitles, spelled out or abbreviated. This lands on that level's table of contents rather than on a section.
-
A level, written the long way
title 11, chapter 5goes to/us/usc/t11/ch5The same destination, in the form prose tends to use.
-
A whole title
title 11goes to/us/usc/t11The title's table of contents. 11 usc, with nothing after it, means the same thing.
-
A note
11 usc 523 notegoes to/us/usc/t11/s523The trailing note is recognised and you land on the section, whose notes are on the page. There is no separate route for notes, so the word is read and then set aside.
-
A run of sections
16 usc 45f et seq.goes to/us/usc/t16/s45fet seq. names a run starting at a section. You land at its start; there is no view of a range.
-
Wrapped in brackets
(11 U.S.C. 523)goes to/us/usc/t11/s523Enclosing brackets, quotes and trailing punctuation are stripped, so a citation pasted from the middle of a sentence works. Brackets that belong to the citation are kept: 523(a)(1) is read as a subdivision.
Two things that will catch you out
-
523not read as a citationA section number with no title is unresolvable, because many titles have a § 523. Typed on its own it is treated as a word and searched for.
-
5 U.S.C. App. 3parses, finds nothingAppendix citations parse and then find nothing. The five appendix titles are published under the enacting instrument, not a flat section number: 0 of 461 appendix sections use this shape, and they look like /us/usc/t5a/pl/92/463/s1. Getting from one form to the other needs a lookup table this site does not have.
Searching the text
By default a search matches the words you typed, and every one of them has to appear. The operators below are how you loosen that deliberately — including asking for near-spellings when you are not sure how a word is written.
Strict by default
Searching for compare finds provisions containing the word
compare — not compact or company. This site used to
return all three, because it ran every search with a two-character-edit
tolerance nobody asked for. In a body of law a different word is a different
rule, so that tolerance is now something you request.
If you are unsure of a spelling, add ~1 to the word: conservation~1 finds
provisions containing anything within one character edit of it.
Operators
-
"…"Exact phraseThe words in that order, next to each other. Without the quotes both words must still appear, but anywhere in the provision and in any order.
-
~nMisspellingsAlso matches words within n single-character edits — one insertion, deletion, substitution or transposition each. Use it when you are unsure of a spelling. Keep n at 1 or 2: at 2, six-letter words start matching genuinely unrelated ones.
-
*Word beginningMatches any word starting with those letters — navigable, navigability, navigation. Only at the end of a word; a leading * is not supported, because matching every word by its ending would mean scanning the whole index.
-
"…"~nWords near each otherThe phrase, but allowing up to n words in between and in either order. Useful when you know two terms belong together but not exactly how they are written.
-
-ExcludeExcludes provisions containing the word. The minus goes immediately before the word, with no space after it.
-
+RequireRequires the word. Rarely needed here, because every word is already required by default — it matters only when you have written an | somewhere in the same query.
-
|Either wordMatches provisions containing either word. Use it to loosen a search that is finding too little.
-
( )GroupingGroups terms so the operators apply the way you meant, exactly as in arithmetic.
-
\Literal characterTreats the next character as text rather than as an operator — for searching a phrase that genuinely contains a hyphen or a quotation mark.
-
SpaceA space separates terms, and all of them must be present. This is the default, so every word you add narrows the search.
What is searched
The text of sections and the headings above them — chapters, subchapters, parts. A search covers the law currently in force unless you name a release point, which is done from the URL and is described in the next section.
Searching at a release point
You can search the Code as it stood at a past release point. This is the one place on the site where the answer is not yet complete, so both halves are set out below: how to ask, and what comes back.
The search box has no control for this yet, so you add the release point to the results URL. There are two parameters, the same two a citation URL takes: the label of a release point, or a date.
-
&release=by release pointThe label as the Office of the Law Revision Counsel writes it, awkward ones included:
119-102not101is current through Public Law 119-102 except 119-101. The release points page lists them all. -
&date=by dateMM/DD/YYYY, resolved to the release point in force on that day. Usually easier than looking up a label. The results page names the release point it landed on, so you can see which one answered.
Not the whole picture yet
The search index currently holds the text in force — one document per section, as it reads today. A search at a release point therefore finds the provisions whose current text was already in force then, and it misses text that has since been replaced: a section amended in 2024 cannot be searched as it read in 2019, even though the reader will happily show you that version.
What is missing is the index, not the feature. Every superseded version is in the
database and the indexer knows how to write them — python -m ingest.reindex_search --all-versions builds them, roughly
490,000 documents against the 66,000 the default search reads. It has not been
run against this deployment, and until it is, a point-in-time search is answering
from current text alone.
You can always tell which you got: the results page says either “In the text as of release point …” or “Searching the law currently in force.”
Asking what cites a provision
Prefix a citation with cites — cites 26 usc 501 — and the search looks for provisions that refer to it. This is a keyword search
over the citation's text for now, not a real cross-reference index, and the results
page says so rather than letting the answer pass for the finished thing.