Check the structure
Spot missing required details, unreadable dates, and repeated event identifiers in one pass.
Read an iCalendar file as a useful timeline. Find missing dates, repeated event IDs, and time-zone warnings before you rely on an export.
File contents and requested calendar text are checked in memory and aren’t saved to an account. Private feed URLs can act like passwords; check only a link you’re authorized to use.
▣ One-time check. No account needed.
Start with a file you already have. Understand what may affect the next import or calendar update.
Spot missing required details, unreadable dates, and repeated event identifiers in one pass.
Review a simple event timeline without importing guest calendars into another service.
Keep each event’s source wall-clock time and TZID visible, including daylight-saving changes and undefined-zone warnings.
Create a free account to save one feed for daily server checks, a private 30-day history, and optional email alerts when the feed changes or a check finds a problem. Feed URLs are stored encrypted. Need more than one feed? The multi-feed plan covers up to 10.
The current version parses iCalendar files and reports required-field, date-range, duplicate UID, and time-zone observations. It does not contact Airbnb, Vrbo, or Booking.com.
No. A structurally readable file does not prove that an external platform fetched it, interpreted every recurrence, or updated availability on time.
One-time checks are processed on the server and are not saved. If you create an account, only the feeds you choose to monitor are stored — the URL encrypted, with a private 30-day history of check results. Do not upload files containing private guest details.
The parser follows iCalendar data structures from RFC 5545. This early checker covers selected fields and is not a full standards conformance certificate.