In the "Data state", an "end-of-file token" is emitted:

> EOF
>     Emit an end-of-file token. 


In the Tree Construction Definitions, an "EOF token" is mentioned:

> next input token
>     The token following the current input token in the list of tokens produced by the tokenizer. If there isn't a token following the current input token, the next input token is an *EOF token*.


In the "Top-level mode", "At-rule-prelude mode", "Rule-block mode", and several other modes, an "EOF token" is expected. E.g.:

> EOF token
>     Finish parsing. 


However, neither "EOF token" or "end-of-file token" is mentioned in the list of possible tokens in the Tokenization overview:

> The output of the tokenization step is a series of zero or more of the following tokens: identifier, function, at-keyword, hash, string, bad-string, url, bad-url, delim, number, percentage, dimension, unicode-range, whitespace, comment, cdo, cdc, colon, semicolon, [, ], (, ), {, }.