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.
Once account setup is open, each account can monitor one encrypted feed URL with daily server checks and private 30-day history. Signup is currently closed while email verification and encryption settings are configured. Optional alerts are available when a verified email and mail delivery are configured; paid plans are not for sale.
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-file checks are processed on the server and aren’t saved to an account. This first version keeps no result history. 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.