Thank you for the suggestion! We don't think we'll have time in the coming year to add this, but we appreciate hearing from you and will get back to you if we begin implementing this feature.

Thanks for your message. According to our calendar, April 9, 1942 (before sundown) is the 8th day of Pesach, not the 7th day of Pesach:

Thu, 9 April 1942 = 22nd of Nisan, 5702

כ״ב בְּנִיסָן תש״ב

Parashat Shmini

7th day of the Omer

🫓 Pesach VIII 🫓 in the Diaspora

If you click after sunset you will see this:

Thu, 9 April 1942 after sunset = 23rd of Nisan, 5702
כ״ג בְּנִיסָן תש״ב
Parashat Shmini
8th day of the Omer

Note the Hebrew date is displayed in two different places:

In Hebrew: כ״ג בְּנִיסָן תש״ב

In transliteration: 23rd of Nisan, 5702

Thanks for the bug report! We are terribly sorry for this inconvenience.

The issue has been fixed and the URLs work correctly once again.

You should celebrate your birthday every year!

Hebcal uses the anniversary algorithm defined in Calendrical Calculations by Edward M. Reingold and Nachum Dershowitz, which accords with Ashkenazic practice. Reingold and Dershowitz write:

Someone born on the thirtieth day of Marcheshvan, Kislev, or Adar I has his birthday postponed until the first of the following month in years where that day does not occur. [Calendrical Calculations p. 111]

In other words, on years where there is no 30th of Kislev, your birthday is celebrated on the 1st of Tevet.

Feature was released on December 1 and is currently available. Please give it a try and let us know how it works for you!

Thanks for the suggestion. Effective December 2025, we now support Hebrew dates in the Yahrzeit API as an alternative to Gregorian dates:

• hyX=5749 – Hebrew year
• hmX=Kislev – Hebrew month
• hdX=25 – Hebrew day of month

Hebrew month names may be specified in Hebrew (UTF-8) or transliterated using the same technique as on the Hebrew Date Converter REST API.

Please give it a try and let us know how it works for you!

Glad you were able to get this worked out!

Yes, we discovered a DNS error and fixed it last night. Our sincere apologies!

can you send a screenshot? We don’t see any errors 

when using the API, to get the next occurrence, omit the start and end parameters, and specify years=2. Then, in the returned results, examine the date in the first item. If the date is before today, then ignore the first item and use the second item. If the date of the first item is today or later, then the first item is the next upcoming observance.