Nokia PC Suite Content Copier file (.nfc)
.nfc file signature | application/octet-stream
Magic Bytes
Offset: 0
03 00 00 00
Nokia PC Suite Content Copier file
Sources: Gary Kessler
Validation Code
How to validate .nfc files in Python
def is_nfc(file_path: str) -> bool:
"""Check if file is a valid NFC by magic bytes."""
signature = bytes([0x03, 0x00, 0x00, 0x00])
with open(file_path, "rb") as f:
return f.read(4) == signature
How to validate .nfc files in Node.js
function isNFC(buffer: Buffer): boolean {
const signature = Buffer.from([0x03, 0x00, 0x00, 0x00]);
return buffer.subarray(0, 4).equals(signature);
}
How to validate .nfc files in Go
func IsNFC(data []byte) bool {
signature := []byte{0x03, 0x00, 0x00, 0x00}
if len(data) < 4 {
return false
}
return bytes.Equal(data[:4], signature)
}
API Endpoint
/api/v1/nfc
curl https://filesignature.org/api/v1/nfc
See the full API documentation for all endpoints and parameters.
Frequently Asked Questions
What is a .nfc file?
A .nfc file is a Nokia PC Suite Content Copier file file. Nokia PC Suite Content Copier file
What are the magic bytes for .nfc files?
The magic bytes for Nokia PC Suite Content Copier file files are 03 00 00 00 at byte offset 0. These bytes uniquely identify the file format regardless of the file extension.
How do I validate a .nfc file?
To validate a .nfc file, read the first bytes of the file and compare them against the known magic bytes (03 00 00 00) at offset 0. This is more reliable than checking the file extension alone, as extensions can be renamed.
What is the MIME type for .nfc files?
There is no officially registered MIME type for .nfc files. Systems typically use application/octet-stream as a generic fallback when handling this format.
Is it safe to open .nfc files?
Nokia PC Suite Content Copier file (.nfc) files are generally safe to open. They are classified as low risk because they primarily contain data rather than executable code. However, always ensure files come from a trusted source.