MRPL40 Polyclonal antibody
MRPL40 Polyclonal Antibody for WB, IHC, IP, ELISA
Host / Isotype
Rabbit / IgG
Reactivity
human
Applications
WB, IHC, IP, ELISA
Conjugate
Unconjugated
Cat no : 16767-1-AP
Synonyms
Validation Data Gallery
Tested Applications
Positive WB detected in | A549 cells, HeLa cells, HepG2 cells, K-562 cells |
Positive IP detected in | HeLa cells |
Positive IHC detected in | human ovary cancer tissue Note: suggested antigen retrieval with TE buffer pH 9.0; (*) Alternatively, antigen retrieval may be performed with citrate buffer pH 6.0 |
Recommended dilution
Application | Dilution |
---|---|
Western Blot (WB) | WB : 1:1000-1:6000 |
Immunoprecipitation (IP) | IP : 0.5-4.0 ug for 1.0-3.0 mg of total protein lysate |
Immunohistochemistry (IHC) | IHC : 1:50-1:500 |
It is recommended that this reagent should be titrated in each testing system to obtain optimal results. | |
Sample-dependent, Check data in validation data gallery. |
Product Information
16767-1-AP targets MRPL40 in WB, IHC, IP, ELISA applications and shows reactivity with human samples.
Tested Reactivity | human |
Host / Isotype | Rabbit / IgG |
Class | Polyclonal |
Type | Antibody |
Immunogen | MRPL40 fusion protein Ag10341 相同性解析による交差性が予測される生物種 |
Full Name | mitochondrial ribosomal protein L40 |
Calculated molecular weight | 206 aa, 24 kDa |
Observed molecular weight | 18-24 kDa |
GenBank accession number | BC009707 |
Gene symbol | MRPL40 |
Gene ID (NCBI) | 64976 |
Conjugate | Unconjugated |
Form | Liquid |
Purification Method | Antigen affinity purification |
Storage Buffer | PBS with 0.02% sodium azide and 50% glycerol pH 7.3. |
Storage Conditions | Store at -20°C. Stable for one year after shipment. Aliquoting is unnecessary for -20oC storage. |
Protocols
Product Specific Protocols | |
---|---|
WB protocol for MRPL40 antibody 16767-1-AP | Download protocol |
IHC protocol for MRPL40 antibody 16767-1-AP | Download protocol |
IP protocol for MRPL40 antibody 16767-1-AP | Download protocol |
Standard Protocols | |
---|---|
Click here to view our Standard Protocols |