Shapefile · dBASE III/IV
What you are seeing — your columns came back as beschermin, sitecode_v and individual, and the names you actually gave them are gone.
The cap is real and it is not in the shapefile specification. The spec delegates the attribute table wholesale to dBASE. Two other facts produce the 10: the dBASE III/IV field descriptor allots 11 bytes for a name, and ESRI's own software caps it at 10 (ArcGIS error 000142).
That distinction matters if you are writing a reader — believing the cap is 10 in the format cuts one character off any name that fills all 11 bytes, silently. We read 11 bytes and stop at the first NUL.
For everyone else the consequence is simpler and worse: the original spelling is not recoverable from the file. The export destroyed it before you ever saw it. Nothing can undo that — not us, not a GIS, not the person who sent it, unless they still have what they exported from.
It is also why a column should be confirmed from its values rather than its header. scientific could be a scientific name or a scientific method; the values settle it and the header cannot.
If you are choosing a format now, this is the strongest single argument for GeoPackage: it has no cap at all.
Drop the zipped bundle or the bare .dbf and we will name every column that hit the cap. Free during the testing period · no account needed · without one, what we read is kept to teach the reader, names removed; sign in and nothing is kept.