How can we
help you DX?

LOG11DX is a logging and DX cluster-style platform built specifically for the 11 meter band (27 MHz). It combines:

• Live DX spots feed (table + map)
• DX Radar opening summaries
• Personal QSO logbook (“My log” / private log)
• Built-in eQSL system
• Activation tools (special calls, activator dashboard)
• Chat and private messaging between users

For 11 m CB / freeband DXers who want DX alerts, a proper online log, and an easy way to exchange QSLs.

Yes. SWL operators can use LOG11DX to follow spots, maps and activity. The main logbook and eQSL flow are built around station-to-station QSOs, so use the normal logging fields only when they match the activity you are recording.

LOG11DX is mainly operated in English. Some help videos and community support may be available in other languages, and your browser translation tool can help with the interface if needed.

You can view a lot of things as a guest, but to log QSOs, send/receive eQSLs, use private messages and activations, you need a free account.

• Your base callsign is stored in your profile (e.g. CALLSIGN).
• You can add things like /QRP, /M, /P in your profile so it shows e.g. CALLSIGN/QRP where it makes sense.
• For special events you can use activation callsigns (e.g. CALLSIGN/ACT) via the activation system.

An activation callsign is a special callsign used for a certain activity (island, lighthouse, SOTA-style, event, etc.). You can manage these on the Activator pages (create, set current, archive).

In your profile you can:

• Set your display callsign behavior (normal/activation/QRP etc.)
• Upload avatar/profile picture
• Set QRP, /M, /P etc. so they appear correctly on eQSLs and spots
• Configure default use of current activation (when available)
• Keep one default eQSL and add dedicated operating / activation eQSL cards for exact callsigns like NN/CALLSIGN

Yes. In your profile you can keep your normal default eQSL and also add dedicated cards for exact operating callsigns such as NN/CALLSIGN or an activation callsign. LOG11DX will try to use the exact matching card first, then fall back to your default eQSL if no special card exists for that identity.

A DX spot is a short report that a certain station (DX) was heard or worked on a specific frequency, mode and time. The front page shows a live stream of spots in table form and on the world map.

1. Use the LOG DX button from the front page or Dashboard v2.
2. Fill in DX callsign, frequency, mode, UTC time, path, report and other details.
3. Choose whether the entry is just for your logbook or also published to the live public feed.
4. Save the entry – private entries stay in your logbook, public entries also appear in the live table and map.

• Public log shows the shared live DX feed for the site.
• Private log is your own QSO history where you can edit entries, send eQSLs and manage your station details.

Yes. LOG11DX is connected to the wider 11 meter cluster family so your public spots can travel further than one website. When you make a public spot on LOG11DX, it goes first to the CRX Cluster. From CRX it is shared onward to our connected partner clusters.

Spots made on LOG11DX can take up to about 3 minutes before they appear on other clusters. Cluster sharing is very reliable, but it is still a live network between different systems, so around 98% of spots should be expected to show everywhere – not always 100%.

We currently share spots with:

• Rcqsl – Rome Charlie Group
• 11dxNet
• CRX11m
• Lf11
• 11Mc
• N1
• Cluster446fr
• irdcluster
• DxteleNet
• Cluster_Dk
• Dx27
• Dxqsm
• RadioCluster

There is also a nice bonus for registered LOG11DX users: if you make a QSO spot on 11DxNet and your callsign is registered on LOG11DX, that spot is automatically added to your private LOG11DX logbook. It keeps your logbook up to date even when you are spotting from another connected cluster.

• One marker shows the DX station (country/location).
• One marker shows the spotter (your location, if available).
• A red line is drawn between spotter and DX to visualize the path.

The “Today / All” controls both the table and the map, so you can view only today’s activity or the wider data set (depending on how many spots are loaded).

• Live Spots is the current public spot count shown on the front page.
• Hot Freq is the busiest recent frequency based on current activity windows.
• DX Highlight is a featured country/callsign from the current live feed. It is a live spotlight, not an official rarity ranking.

Use the Members page, Live Map or spot filters to search by callsign, country, division prefix or recent activity. If a callsign is not registered and has not appeared in public activity, LOG11DX may not have profile details for it.

Yes. LOG11DX supports logbook export and import, including ADIF and other supported formats. Exported files now use a clean log11dx_log filename, so your downloaded files stay easy to recognize.

After an import, LOG11DX shows a clearer summary of how many spots were imported and how many duplicates were skipped. That makes it much easier to see whether the file added new QSOs or only matched spots you already had in your private log.

Yes. If you re-import a LOG11DX export, the system can identify it as a log11dx.com file in the import result message.

DX Radar groups current propagation activity into regional opening cards such as South America, Caribbean, UK & Ireland, Nordics or Mediterranean. It is a live summary layer designed to help you see where conditions are building, not a guaranteed contact prediction system.

• Strengthening means activity is building in that region.
• Opening means the region is actively showing recent confirmed/ghost evidence.
• Active means the region still has current activity, but it is not rising as sharply.

• Watch which regions start strengthening, then check the live spot table for exact frequencies and callsigns.
• Use it as a shortcut to where propagation may be moving next.
• Combine it with the live map, Hot Freq card and current public spot feed for the best picture.

DX Radar is live, but it is still a summary system. Cards update from recent spot activity and are meant to guide you quickly, not replace the actual spot table.

On the main DX spots view you can open the Filters panel to narrow down the list. For example:

• Mode (SSB, FM, Digital, etc. – multi-select)
• DX callsign or spotter callsign
• Date/time ranges
• Frequency range
• Country and path
• Source/node
• “Registered only” – hide spots from non-registered users
• “My spots” – show only spots and QSOs that you logged

• The live DX stream is paused (so your results don't jump around).
• A banner appears to tell you filters are active.
• Pagination / “Load more” is adjusted for filtered results.

Yes. The front-page summary cards refresh automatically in the background, and the live spot count updates immediately as new rows are inserted or removed.

If you tick “Remember these filters & auto-apply next time”, your settings are saved for your user and automatically loaded the next time you visit.

LOG11DX has its own eQSL system. You can send and receive electronic QSL cards based on QSOs logged in the system. The card includes the usual details (callsigns, date/time, frequency, mode, RST etc.).

1. First, log the QSO.
2. Go to your private log / “My log”.
3. Find the QSO and click the “Send eQSL” button.
4. Check the details and confirm sending.

LOG11DX supports automatic eQSL handling for newly saved QSOs. If your profile eQSL auto option is enabled, eligible new log entries can automatically create the eQSL and mark the QSO as sent. If the auto option is disabled, nothing is auto-sent, but you can still send eQSLs manually from your private log at any time.

LOG11DX uses the exact operating identity of the QSO whenever possible. That means a QSO logged as NN/CALLSIGN can use a dedicated NN/CALLSIGN eQSL card, while normal CALLSIGN QSOs can still keep using your default card. Older sent cards do not change afterward.

1. Go to Profile.
2. Find eQSL settings.
3. Save your preferred eQSL auto setting there.

When an eQSL arrives in your inbox, LOG11DX attempts to match it to a QSO in your logbook. If it matches, it is stamped automatically. Matching uses:

• ±15 minutes (UTC)
• ±5 kHz (frequency)

If an inbound eQSL can't be matched, it will show Not in your log with an Add to logbook button. One click will create the missing QSO entry for you.

Yes. You can send an eQSL even if the other station has not yet created an account. When they register later with the same callsign, the eQSL will be waiting for them.

LOG11DX can match registered users through their normal callsign, working prefix and activation display callsign. So if a registered user is operating as NN/CALLSIGN, eQSL delivery can still go to that same account instead of being treated like a guest-only callsign.

Deleting an eQSL removes it only from your own view. It does not remove the other station's copy. This lets the receiver keep the card even if the sender later hides it from their own inbox or sent list.

The system tries to show your correct active identity: base callsign, any suffix like /QRP, and activation callsign if you are using one. If you change your profile or activation settings, only new eQSLs will follow the new setting – older cards stay as they were sent.

An activation is a special event where you operate from a specific location or under a special event callsign, for example 21AT/DOOM. Activation QSOs are saved in a separate activation logbook so they do not mix with your private log until you choose to import or handle them.

1. Go to Profile and open the Activations area.
2. Enter the activation callsign, code, grid, label, frequency and mode.
3. Click Start Activation.
4. If you want a special card for this activation, upload the activation eQSL when LOG11DX asks. If you skip it, your default eQSL card is used.
5. Open the logger and start adding QSOs.

• Log activation QSOs with progressive numbers.
• Edit or delete individual activation QSOs.
• See worked countries, continents, total points and the world map.
• Send one eQSL for a single QSO, or send activation eQSLs in bulk.
• Export the activation log as ADIF, CSV or PDF.
• Use the activation callsign on sent eQSLs, including the correct date and UTC time.

Activation eQSLs use the activation callsign, not your normal account callsign. LOG11DX first looks for an exact activation eQSL card for that activation callsign. If no special activation card exists, your default eQSL card is used. Activation eQSLs also use default 5/9 reports when the activation logger does not collect RST manually.

Yes. Use the small eQSL/send button on a QSO row to send one card, or use the bulk activation eQSL button to send cards for the activation log. Bulk sending uses the same QSO details as one-by-one sending and skips QSOs that already have an eQSL.

Replies arrive in your normal eQSL inbox. If both sides have exchanged cards for the same QSO, LOG11DX marks the eQSL as exchanged.

• End Activation stops the live activation.
• Archive hides a finished activation from the active list but keeps its history.
• Restore brings an archived activation back to the visible list.
• Delete log is separate and should only be used when you really want to remove the activation log data.

Operating prefix logging is for normal QSOs made while you are operating from another division or with a temporary operating identity, for example 15/21AT106, 21AT106/P, 21AT106/M or 21AT106/QRP. These QSOs stay in your normal private logbook.

1. Go to Profile and open Operating Setup.
2. Choose a suffix if needed, such as /P, /M or /QRP.
3. Enter the operating prefix if you are working from another division, such as 15/.
4. Click Save. Leave the prefix empty to clear it.

In Profile, open Operating eQSL to upload exact-match cards for operating identities. If you log as 15/21AT106, LOG11DX first looks for an eQSL card saved for 15/21AT106. If no exact card exists, your normal default eQSL card is used.

• Activation logging uses the separate Activation Logger and an activation callsign such as 21AT/DOOM.
• Operating prefix logging uses your normal private logbook with your temporary operating identity such as 15/21AT106 or 21AT106/P.
• Both can use special exact-match eQSL cards, but they are managed in separate profile areas.

For each spot/log the system stores a display callsign. This may be:

• Your normal callsign
• Your normal callsign with suffix (/QRP, /M, /P)
• Your current activation callsign (if you choose to use it)

That “display callsign” is what other users see in tables, map, chat and eQSLs.

The LOG11DX WSJT Bridge is a small Windows app that connects WSJT-X or WSJT-CB on your computer to your LOG11DX logbook. It listens locally for completed logged QSO messages from WSJT and uploads them to LOG11DX through a secure API token. Version 1.5.0 also includes DX Radar for live local decoded activity, voice alerts, opening summaries and WSJT-CB Prepare.

Only completed QSOs that you log in WSJT-X / WSJT-CB are uploaded. Normal decoded traffic from DX Radar is not sent to LOG11DX.

• Callsign
• Date and time
• Frequency and band
• Mode, such as FT8
• Sent and received reports
• Grid, operator/name and comments when WSJT provides them

Completed WSJT QSOs are always saved to your private LOG11DX logbook first. Public sharing is optional and turned off by default. If you enable Publish WSJT QSOs publicly in your profile, those QSOs are also shared to the public LOG11DX spot feed. If your account is set to share public spots with other clusters, public WSJT spots follow that setting too.

1. Log in to LOG11DX and open your profile.
2. Go to WSJT-X / WSJT-CB Integration.
3. Click Generate new API token and copy the token immediately.
4. Download and open LOG11DX WSJT Bridge.
5. Paste the token into the bridge app, or use the Paste Token button.
6. Click Check Token to confirm the connection.
7. Leave UDP host as 127.0.0.1 and UDP port as 2237.
8. Click Save Settings, then Start Bridge.

In WSJT-X / WSJT-CB reporting settings, set the UDP server to:

• UDP server: 127.0.0.1
• UDP server port: 2237

Then log QSOs normally in WSJT. When a QSO is logged, the bridge should show messages such as Uploaded, Duplicate skipped, or Token invalid.

DX Radar is a local monitor inside the bridge. It shows live decoded activity, CQ/QRZ callers, mode, signal, grid, country, status, map markers and current opening summaries. It is designed to help you see useful activity faster, but it does not upload decoded traffic to LOG11DX.

Open the DX Radar tab and click Alert Settings. You can enable a simple alert sound, voice alerts, choose a Windows voice, select short or detailed speech and test the voice before saving. Voice alerts use Windows text-to-speech and work locally on your computer.

Yes. In DX Radar alert settings, use Clean DX Radar Cache. This clears saved startup spots and recent voice-alert memory. It does not stop live decoding and does not change your logbook.

In WSJT-CB, open File > Settings > Reporting and enable Accept UDP requests. Recommended settings are:

• UDP server: 127.0.0.1
• UDP server port: 2237
• Outgoing interface: loopback_0, if available

In the bridge DX Radar list, double-click a real CQ or QRZ decode and choose Prepare only. This prepares the call in WSJT-CB. It does not transmit.

No. A plain double-click never transmits. Prepare only does not transmit. Enable TX requires that TX control is enabled in bridge settings and that you confirm it. You are always responsible for your own transmission.

No. The bridge uses only the WSJT API token from your profile. If a token is lost or you no longer trust it, revoke it in your profile and generate a new one.

Network or server failures are queued locally by the bridge and retried later. Duplicate QSOs are skipped safely by LOG11DX, so restarting the bridge should not create repeated log entries for the same QSO.

Diplomas are achievement awards based on your LOG11DX activity. When your logbook reaches a diploma requirement, that diploma becomes available in your Diploma Cabinet.

• Worked DXCC: unique DXCC entities/divisions you have worked.
• Confirmed DXCC: unique entities confirmed by QSL or eQSL.
• QSOs: worked log entries marked WRK in your private logbook.
• Spots posted: public spots you have posted from your account.
• Quality spots: your posted spots that later produce at least one logged QSO.

DXCC diplomas count unique entities, not every QSO row. If you work the same entity many times, it still counts once for that DXCC milestone.

Open Diploma Cabinet. Available diplomas appear in the claim list. Click Claim 1 now to claim the next available diploma, then download the JPG from your claimed diplomas list.

The important part of a diploma is the milestone itself, such as Worked DXCC 100, Confirmed DXCC 50 or 500 QSOs. Bronze, Silver and Gold are still used as visual level badges, but the award name should make the target clear when you show it to another operator.

Each claimed diploma gets a unique verification code and QR link. Anyone can open the verify link to confirm that the diploma was issued by LOG11DX.

Rarity is based on how many operators have claimed that exact diploma. Very low claim counts are shown as legendary or rare.

A donation certificate is an official LOG11DX supporter certificate for a year where you have at least one completed donation and an active supporter status.

No. Certificates are issued once per donation year. For example, if you donated once in 2025 and three times in 2026, you normally have two certificates: one for 2025 and one for 2026.

The certificate level is based on your lifetime completed donations:

• Bronze: 1 completed donation
• Silver: 2-3 completed donations
• Gold: 4 or more completed donations

The certificate still belongs to a specific year, but the supporter level shows your lifetime support. Once you reach Gold, new and regenerated certificates use the Gold level.

Open My Certificates, choose the year, and generate the certificate if it is available. Existing certificates can be downloaded as JPG.

You can also start from your Profile and look for the Certificates area. If you supported LOG11DX but do not see a certificate, contact support so your supporter status can be checked.

Every certificate has a unique ID and a server signature. The verify page checks that the ID, user, year, supporter tier and donation trigger still match the official LOG11DX record. If the signature does not match, the certificate is shown as invalid.

A mismatch usually means the saved certificate record and the verification signature no longer agree. Contact an admin instead of deleting it yourself; admins can repair the certificate signature while keeping the same certificate ID.

There is a built-in chat where you can talk to other users in real time (within the rules of the community – be nice).

You can send direct messages to other registered users. The navbar shows a PM icon with a counter when you have new messages. PMs support normal text messaging, and image sending is available on the inbox/profile message flow.

When you receive an eQSL, you get a notification and an unread counter on the eQSL icon in the navbar. Open your eQSL inbox to view, download or print.

• Public DX spots are visible to everyone (or to logged-in users if the filter says “registered only”).
• Your private log is visible only to you.
• eQSLs are visible only to the two stations involved.

You can edit or delete your own spots from the table / private log. Deleting a QSO may also remove or invalidate eQSLs linked to it.

An Invalid CSRF or security-token message usually means the page was open too long, the form token expired, or your login session changed. Reload the page and try again. If it still happens, log out, log back in, and repeat the action from a fresh page.

If something looks wrong (callsign display, eQSL info, activation data, etc.), please contact an admin via PM or use the support channel mentioned in the chat.