TAR File Check

TAR FILE CHECK

Check a TAR file

Inspect a .tar archive for header checksum problems, malformed member sizes, truncated data, block-padding issues, unsafe extraction paths, and archive-end warnings — directly in your browser.

Drop your TAR archive here
or
TAR · or a file you suspect should be a TAR archive
The selected TAR archive is inspected locally in your browser. Member contents are not executed or uploaded to ARADURU.
No upload Designed for local processing No account Start without signing up Clear results Understand what went wrong
WHEN TO USE THIS CHECK

TAR archive won’t extract or looks incomplete?

Start with the archive structure itself. ARADURU checks TAR member headers and block boundaries before you assume the extraction application or archived files are the problem.

The TAR file will not extract Check whether member headers, checksums, sizes, data blocks, and padding stay consistent through the archive.
An archive tool reports an unexpected EOF Look for a member whose declared data or 512-byte padding extends beyond the selected file.
The archive may have a damaged header Verify the checksum stored in each parsed TAR member header before trusting its size and boundaries.
You want to review extraction-path warnings Identify member names that may escape a normal extraction directory if an extractor does not sanitize paths.
Check my TAR file ↑ No account. The selected TAR archive stays in your browser.
WHAT ARADURU CHECKS

Structure checks across the TAR archive

ARADURU walks TAR members on 512-byte boundaries and verifies file-side evidence without extracting member contents to the server.

01

Header checksums

Compare each stored TAR header checksum with the bytes in its 512-byte member header.

02

Member sizes

Parse standard TAR size fields and stop safely when a member boundary cannot be determined without guessing.

03

Data boundaries

Confirm that each declared member payload remains inside the selected TAR archive.

04

Block padding

Check the 512-byte padding needed before the next TAR member header can begin.

05

Archive-end marker

Review the zero-block end marker and distinguish a missing or incomplete marker from a direct member-corruption error.

06

Extraction paths

Flag member paths that may escape a normal destination directory if an extractor does not sanitize them.

WHAT THIS DOES NOT GUARANTEE

A healthy TAR archive does not prove every member file is healthy.

ARADURU checks the TAR container, member headers, checksums, sizes, block boundaries, and extraction-path evidence. Each archived file can still require its own format, syntax, security, or application-specific check after extraction.

  1. Keep the original. Extract or repair a copy when the archive matters.
  2. Use a trusted extractor. Prefer software that sanitizes member paths before writing files.
  3. Check extracted files separately. A healthy TAR wrapper does not validate each archived file.
  4. Use Upload Check. Compare the .tar file with a destination’s size, type, and filename rules.