Contact
Found a pattern, timing or accessibility issue? A clear example helps us fix it.
Prepare a correction
Email morsebeacon@gmail.com to report a correction. You can also save a report below to attach later; the form sends nothing.
Useful details to include
- The page address and text or Morse you entered.
- The result you expected, with an ITU or ARRL reference for a code correction.
- Your device and browser, and whether sound, microphone or camera was involved.
Please leave out passwords, private recordings and personal details.
Check the result before reporting
For typed dots and dashes, compare the result with the Morse alphabet chart and try the decoder with spaces between letters. An audio or camera result depends on clear timing and the signal that actually reached your device. If a live result is wrong, save that tool’s signal report and describe the message you sent, the displayed result, your speed and the phone or browser you used.
For an error in a phrase guide, include the phrase page address and the exact word or letter that looks wrong. The checking method explains the standards behind the table. If your concern is about a shared link or local recording, read the privacy policy before including any personal information.
Checked against ITU-R M.1677-1 · Last reviewed · How we check our pages · Report it