Text search
Select the Search tab of the toolbar to search this site:
- Select a data set from the Search in drop-down list.
- Enter your query in the Query field.
- Click the Search button.

Query syntax
Here is a brief overview of the supported query syntax (see also query fields for UniProtKB):
human antigen |
All entries containing both terms. |
human AND antigen |
|
human && antigen |
|
"human antigen" |
All entries containing both terms in the exact order. |
human -antigen |
All entries containing the term human but not antigen. |
human NOT antigen |
|
human ! antigen |
|
human OR mouse |
All entries containing either term. |
human || mouse |
|
antigen AND (human OR mouse) |
Using parentheses to override boolean precedence rules. |
anti* |
All entries containing terms starting with
anti. Asterisks can also be used at the
beginning and within terms. Note: Terms
starting with an asterisk or a single letter followed by an
asterisk can slow down queries considerably. |
author:Tiger* |
Citations that have an author whose name starts with
Tiger. To search in a specific field of a
dataset, you must prefix your search term with the field
name and a colon. To discover what fields can be queried
explicitly, observe the query hints that are shown after
submitting a query or use the query builder (see
below). |
length:[100 TO *] |
All entries with a sequence of at least 100 amino acids. |
citation:(author:Arai author:Chung) |
All entries with a publication that was coauthored by two specific authors. |
To use characters that have a special meaning in the query syntax literally
in your query, you must escape them with a backslash, e.g. use gene:L\(1\)2CB to search for
the gene name L(1)2CB. The current list of special characters
is:
+ - && || ! ( ) { } [ ] ^ " ~ * ? : \
Query builder
To restrict terms to specific fields in advance, click the 'Advanced Search ยป' button. Depending on the chosen data set and field, you can then enter some text or choose values from a drop-down list. Then click the Add & Search button to add the new constraint and run the new query.

See also: Search tips from our FAQ
