ZM4G glow logo
ZL2iFB glow logo
LoTW User Guide
Home
QTH
Station
Antennas
QSL!
Contesting
DXing
Elecraft
Friends
Homebrew
Intruders
Links
LK550
Logger32
LoTW
Pileups
Tokyo HyPwr
TS850 mods
QBL

I’ve created this unofficial user guide for ARRL’s Logbook of The World to supplement the help available from the LoTW site.  It is an incomplete work-in-progress, and in places refers to Logger32.  Feedback and additional content is very welcome.


Quick links

  1. Why should I bother with LoTW?
  2. Joining LoTW
  3. Using LoTW - some Hinson tips
  4. Checking/correcting your CQ and ITU zones and locator in LoTW
  5. Applying for DXCC or WAS awards using LoTW
  6. Archive your LoTW certificate/s and log/s [important - trust me!]
  7. Generate an ADIF of your DXCC credited (granted) QSOs
  8. Find out who else is using LoTW
  9. “Official” help on LoTW
  10. A wishlist for LoTW enhancements


Why should I bother with Logbook of The World (LoTW)?

If you are a serious DXer, you know how frustrating it can be waiting for QSLs to arrive to confirm each new country.  Whether you send QSLs and $$ direct or just hope for cards to arrive via the worldwide QSL bureaux, collecting confirmations on paper can be tedious, not to mention expensive.  Then once you’ve got your tidy little stack of QSL cards and you wish to apply for awards such as DXCC or WAS, you still need to get them checked and verified by the relevant organization. 

Quite simply, LoTW makes the whole process quicker, easier, cheaper and safer.

With LoTW, you upload your log periodically to the ARRL’s LoTW website where it is entered into a database system that cross-matches your QSO details against other uploaded logs, generating electronic confirmations for all QSOs that match.  LoTW confirmations normally come through within days or weeks, as soon as both parties to a QSO upload their logs to LoTW.  The LoTW system can also track your progress towards DXCC, VUCC, WAS and WPX awards and, when you are ready to claim your awards, it handles the application electronically for you.  For QSOs that have been verified in LoTW, there is no need to sort out QSL cards, fill out the application form and submit the cards for verification.  However you may still choose to submit QSL cards for specific DXCC countries or US states for those bands and modes which are not yet confirmed on LoTW ... or you can just be patient in the hope that eventually you will get them all in LoTW anyway.

By the way, there is absolutely nothing stopping you exchanging paper QSLs as well as using LoTW.  Many of us enjoy collecting those picture postcards from exotic foreign places to show off to our ham friends and wow our long-suffering families.  Even if you are not collecting QSL cards, I encourage you to respond to incoming paper QSL requests as a courtesy to other hams.

Back to quick links


Joining LoTW

The process to join LoTW is a little complicated because it is a secure system.  It uses digital certificates to authenticate submitted logs and prevent people uploading false or fraudulent logs for others (authenticated users are trusted to submit accurate logs for themselves!).  So the first stage is to obtain your digital certificate from ARRL.

Obtain your digital certificate from ARRL

  1. Download and install TrustedQSL (TQSL) from here (Windows version).
     
  2. Using TQSL, generate a callsign certificate request .  This involves entering basic station information such as your name and callsign and creating the .tq5 file that you will submit to ARRL.  They then check the details.  US hams’ details are verified using the FCC’s systems.  Non-US hams have to submit a copy of their license by post to get it checked against the certificate request, for their first certificate anyway.  If everything is OK, ARRL emails you back your callsign certificate.
     
  3. Load the callsign certificate onto the system you used to create the certificate request using TQSL.  The certificate is matched up with the certificate request and verified, just in case anything got corrupted on the way.  If it all checks out, you can now start using the callsign certificate to sign your logs and upload them to LoTW ...

Upload your first log to LoTW

  1. Generate an ADIF output file from your logging program containing the QSOs you want to upload to LoTW (i.e. your entire log at the start.  Subsequently, you will normally only send new QSOs since the previous LoTW upload).
     
  2. Electronically sign the ADIF file using TQSL .  This generates a digital signature based on the content of the ADIF file and your private key, allowing ARRL (or indeed others) to verify the data using your public key on your digital certificate.  The digital signature is appended to the QSO data in the ADIF file and saved as a .tq8 file.
     
  3. In your web browser, login to LoTW on the ARRL website and click the Upload tab.
     
  4. Find and select the signed ADIF i.e. the .tq8 file you just saved on your PC and wait for it to upload.  The upload will take a while if you have thousands of QSOs to upload over a slow link but is nearly instantaneous if you are only uploading a few via broadband.  You should see a success message saying that your log has been added to the database import queue.
     
  5. After a short while, check for new LoTW confirmations using LoTW’s reporting tabs for QSOs or awards.  At busy times, you may need to wait a few minutes, possibly a few hours.  Either way, it sure beats waiting months or years for QSL cards!
     
  6. Update your logging program to show the LoTW confirmations received.  Any decent logging program provides a function to download and import the LoTW confirmations.
     
  7. [Mandatory unless you like living dangerously] Backup your log!  Backup your log!

Back to quick links


Using LoTW - some Hinson tips

  • Upload new QSOs to LoTW as often as you can , ideally at least once a month, preferably once a week.  If you are very active, upload new QSOs daily and check your LoTW confirmations at the same time.  Uploading QSOs to LoTW is, in effect, an off-site backup but only of the basic QSO details.
     
  • Keep an eye on the QSO and confirmation counts (top right of most LoTW screens).  As LoTW usage spreads, the proportion of QSOs that are confirmed via LoTW is gradually increasing.  About one in three recent QSOs are confirmed via LoTW.
     
  • If you alter QSOs in your log (for example correcting broken callsigns when QSL cards arrive), you need to re-upload the changed QSO records to LoTW .  While you might be able to extract the changed QSOs and just upload them, the easiest way is to periodically re-upload your entire log since LoTW automatically ignores exact duplicates.  However, please don’t do this too often (no more than, say, once a year) as it wastes computer power and slows the LoTW systems down a bit.  Be nice.  You’ll need to force TQSL to sign and upload the duplicate QSOs.
     
  • Use the award status table to check on your progress towards DXCC, WAS, VUCC or WPX awards, and the quick QSL report to check which QSOs have been confirmed lately.
     
  • Work lots of contests !  Contest stations are more likely to upload their logs to LoTW than most hams.  Most DXpeditions also use LoTW, although some have deliberately waited many months before uploading, ostensibly to complete “checks” but in reality to extort more money from the hams they worked.  This runs counter to the true amateur spirit    :-( 
     
  • Preferentially contact other LoTW users rather than non-users, given the choice.  The LoTW user list is helpful to identify them, especially if you integrate the data in your DXcluster or logbook software (VE7CC’s cluster user program is ideal for this).  This is not about being a clique, simply that you are more likely to get a QSL and do so more quickly via LoTW than by any other means.
     
  • If you are patiently awaiting a LoTW confirmation that seems “overdue”, the DX station may not have uploaded his log in a while (if ever!) or it may have been a busted QSO.  You can check the last time someone uploaded their logs to LoTW here.  If they have uploaded recently but your QSO remains unconfirmed, it might be worth emailing the DX to check for a busted call, or writing it off as a dud.
     
  • You may need the security of a password to unlock access to the secret key on your LoTW certificate, but then again you may not.  If the risk of some reprobate sneaking onto your machine and maliciously signing false logs in your name is low enough to be safely discounted, then feel free to remove the passwords from your certificates in TQSL using the these instructions.  If you do this, you can upload log updates to LoTW from Logger32 with “just” 5 clicks following the instructions on my Logger32 page using a utility entry to call TQSL with the appropriate parameters.
     
  • Tidy out your old LoTW files from time to time.  Once you have sent a .tq5 certificate request to LoTW, received back the .tq6 certificate and loaded it into TQSL, you can safely delete both files.  Same with the .tq8 signed logs that you have uploaded to LoTW: there is no need to keep the .tq8 files any longer after they have been uploaded.  Hang on to your ADIF logs, of course, and any .p12 or .tbk files.  Keep them safe, preferably off-line (e.g. on a CD-ROM or USB memory stick) and off-site (e.g. at the radio club or in cloud storage).
     
  • If you need to download your entire log from LoTW as an emergency backup*, there are at least five options:
    • Use LoTW’s QSO reports to find out all you can about the missing QSOs and re-enter them manually into your logging program (tedious and error prone unless you are only missing a few QSOs);
    • Capture (‘screen-scrape’) the text one-screen-at-a-time from LoTW’s reports: this is also tedious and error prone, and is definitely not recommended;
    • Use the neat online LoTW log download utility by K1MU, without entering any specific QSO criteria;
    • Use this LoTW query page directly (it starts a full log download - thanks to G4LMW for the tip);
    • Use the ‘synchronise log with LoTW’ function in logging programs such as AClog (but not Logger32, unfortunately).

    * Treat this as a last resort: LoTW only stores the basic, minimal QSO details.  Trust me, it is MUCH better to make your own regular off-line and off-site log backups. 

    Have you backed up your log lately?  Do it NOW!

Back to quick links


Checking/correcting your CQ and ITU zone and locator in LoTW

Some hams are either in such a rush or so confused when they join and start using LoTW that they make leeetle mistakes with their zones and locators.  Perhaps the most common mistake is to swap over the CQ and ITU zones.  Some hams evidently know their CQ zone but haven’t a clue about their ITU zones.  If the values are wrong, every LoTW upload thereafter using that certificate and hence any LoTW confirmations will carry the wrong info until eventually someone notices and kindly lets them know.

This is how to check and if necessary correct your zone and locator data:

  1. Even if you think you know them, double-check your CQ zone, ITU zone and locator.

    HINT: if you think your ITU zone number is less than your CQ zone number but you don’t live in Canada, you have probably made a mistake.
     
  2. Export an ADIF version of your log containing all QSOs from the location whose zones or locators you want to correct.  [In Logger32, this means going to "File" then "Export Logs" then "Create ADIF (Adi) file".  Navigate to a suitable directory and give the ADIF file a name.  Do not select "Partial log" as you almost certainly want the whole thing.  I normally select "Export full Country names" here as it lets me check and sometimes correct the DXCC country allocations made by Logger32].
     
  3. Backup your log at this point, not because anything in the rest of this procedure is particularly risky, but just in case.  It is generally safest to backup both the ADIF log (which may contain errors from the export process) and your logging program’s proprietary format (which may contain additional info but is not so portable as the ADIF).  Store the backups safely.
     
  4. Run TQSL and on the top line menu select   "File"   then   "Sign existing ADIF or Cabrillo file".
     
  5. Click a "location" to select it.  You are actually selecting the appropriate digital certificate - if you manage more than one callsign in LoTW, each will have its own "location" defined and you must use the appropriate one to sign the relevant logs.
     
  6. Click the "Edit" button.
     
  7. Enter or check and correct the zone and locator information there.
     
  8. Click "Next" then "Finish".
     
  9. [The "location" you just corrected should still be selected]  Click "OK".
     
  10. Find the ADIF file that you created in step 1 and click "Open".
     
  11. Click "Save" [the signed log file will be saved with the same file name as the ADIF file but with a .tq8 extension, in the same directory as the ADIF file by default].
     
  12. Click "Yes" to confirm that you really want to sign your log [doh! Why else would you be doing this?  Dumb question!].
     
  13. If prompted, enter your TQSL password [to unlock your private key and sign your log with your digital certificate] and click "OK" to sign your log.
     
  14. Login to the LoTW website and upload your signed log (i.e. the .tq8 file)  as usual.  LoTW overwrites your previously-uploaded QSO data with the correct zones etc.
     
  15. [Optional]  If you have more than one location and log to sign and upload, go back to step 1 and run through again for the other info.

Thanks to Chris for helping prepare these instructions, and for correcting his info!

TQSL incorporates basic integrity checks for zones, and version 2 has various improvements that make it easier to use.  It’s definitely worth upgrading if you are running an old version.  To get the current release of TQSL, visit the ARRL LoTW page.

Back to quick links


Applying for awards via LoTW

The LoTW system can automatically track your progress towards ARRL’s DXCC, VUCC and WAS awards, plus CQ Magazine’s WPX award, but first you need to configure it by setting up your award accounts in LoTW.

The DXCC rules allow you to accumulate QSLs from more than one personal callsign (for example if you use a personal contest or vanity call but not a shared/club call), provided all QSOs are made from the same DXCC country.  Under WAS rules, all QSOs must be made from within 50 miles of the same location: if you move more than 50 miles away, you have to re-start your WAS claims from the new QTH.  Configuring LoTW therefore involves telling the system where you operate from.

When LoTW’s DXCC or WAS reports indicate that you have enough QSLs for an award, you can prepare and submit your application online, sending the fee to claim the award.

At ARRL and CQ Mag HQs, the awards checking process using LoTW is much less labour-intensive and quicker than manually checking written applications and QSL cards.  A recent endorsement application of mine was processed overnight.

If you have additional paper QSLs to submit, you can send them to ARRL HQ (necessary for all 160m cards), take them to a ham convention if card-checkers will be present, or send them to your nearest DXCC field checker (in my case, it’s Lee, ZL2AL).  In the DXCC office at HQ, the verified DXCC confirmations from QSL cards are simply added to those confirmed and claimed via LoTW and appear in your LoTW DXCC records.  Be patient and get in touch with the DXCC office if the process seems to have stalled for more than, say, 2 or 3 months.]

Back to quick links


Archive your LoTW certificate/s

If you somehow lose or corrupt your LoTW certificates (for example if your hard drive crashes, you pick up a PC virus, you accidentally delete or overwrite the files, or your shack burns down), you will need to go through the rigmarole of reapplying to ARRL HQ, sending your license again for validation ... unless you had the foresight to make an archive copy,

Archive your LoTW certificates now, before you forget!

How to archive your LoTW certificates (using TQSL version 2):

  1. Run TQSL.
  2. From the menu, select File then Backup Station Locations, Certificates, and Preferences...

    Backup in TQSL 2


  3. Navigate to a convenient directory on your system.
  4. Click Save.
  5. Exit TQSL.
  6. Copy the backup file (called tqslconfig.tbk ) to a suitable archival/long-term storage medium such as (in decreasing order of merit) CD-ROM, DVD-ROM, external hard drive, USB memory stick, Web or cloud backup, another PC, 8” floppy diskette, stone tablet, wax disk, sand impression or notches on a stick.  That’s your archive.
  7. Store your archive safely, well away from your computer and shack (don’t just sling it in the bottom of a drawer: it’s valuable!  Take care of it!). 

To recover lost/corrupted LoTW certificate, location or config data (using TQSL 2):

  1. Run TQSL
  2. Select File from the menu then Restore Station Locations, Certificates, and Preferences...
  3. Find either the backup file (if it is intact) or your archive, and click OK to restore your info.

Tip: use the same process to transfer your TQSL info to a different PC, such as a new PC or a second station PC.  Install TQSL on the second system, then use the restore function to load the info from your archive.

Tip: make a new archive whenever you get a new/replacement certificate, move to a new QTH and set up a new location in TQSL, or when you archive your log (make this a routine every New Year’s Day, when the clocks change to/from daylight savings time, or whenever it suits you).

Backup and archive your log/s too

Be sure to take regular backups of your log or logs .  Backups are handy to recover from little accidents: provide the backup file is OK, you can recover most of your QSOs (up to the last backup) after accidentally corrupting a section of your log, or perhaps deleting or overwriting the whole log file.  Without backups, if your log is damaged or lost, you will lose all record of all the QSOs you’ve ever had, except perhaps for the very basic details of any you have previously uploaded to LoTW or Clublog (both of which only store the bare minimum of QSO information - think of them as last resort backups).  Believe me, it’s a real pain when it happens.  Those who worked Mellish Reef toward the end of a certain DXpedition know what I mean: the vital laptop dropped into the sea while they were leaving the reef.  Ooops.  Luckily QSOs made up to a day or so earlier had already been uploaded to a control station and were safe, but the final QSOs were lost forever to Neptune.  Doh!

Every so often, make an archive too .  Backup your log/s as normal but then copy the backup file/s to suitable offline media such as a CD or USB memory stick, and stash it somewhere safe away from the shack.  Make this a regular thing e.g. once a quarter depending on how active you are - once every thousand QSOs is another way.  At the very least, take a moment to archive your entire log at the start of every new year, and store it safely away.   That way, the most you will lose will be the QSOs you made during the subsequent year and details of any QSLs received since you made the archive: still bad news but not a complete disaster!

Back to quick links


Generate an ADIF of your DXCC credits (granted)

The QSOs that have been confirmed and credited to your DXCC record can be downloaded from LoTW as an ADIF file in order to update your local DXCC records (e.g. in Logger32) automatically, without the need to find and update the status of every credited QSO individually.

Unfortunately, LoTW doesn’t offer a specific report for this so the trick is to use this wonderful little freeware utility by SP7DQR (thanks Marek, what a star!), or the program “ARRL scraper.exe” provided with a recent version of Logger32. 

Marek’s DXCC credit downloader utility asks for your LoTW username and password, then logs in to LoTW.  It generates working lists for all your DXCC records (e.g. DXCC Mixed, DXCC CW etc.) and then one-by-one looks up, finds and downloads the relevant QSO info from LoTW, saving it as an ADIF file.  It is a slow process, taking about 4 seconds per QSO (so for my 1500 credits, the little blue progress bar took about an hour and 40 mins to reach the end stop) but the utility is perfectly happy to churn away in the background whereas I would have gone nuts trying to do what it is doing by hand!

DXCC credits downloader

The next step is to load the DXCC credits into your logging program.  Marek’s utility includes the function to take in your complete ADIF log file, update the DXCC credit status for the relevant QSOs, and output an ADIF log file containing all your credits.  This works much quicker, taking just a few seconds in my case ...

DXCC credits downloader phase 2

The utility adds the credit information to the ADIF using two fields.  For example, the ADIF record for my 10m QSO with TF3Y goes from:

    <BAND:3>10M <CALL:4>TF3Y <CONT:2>EU <CONTEST_ID:8>ARRL 10m <CQZ:2>40 <DXCC:3>242 <FREQ:9>28.094200 <GRIDSQUARE:6>HP94bd <IOTA:6>EU-021 <ITUZ:2>17 <MODE:2>CW <OPERATOR:4>ZM4G <PFX:3>TF3 <QSO_DATE:8:D>20111210 <RST_RCVD:3>599 <RST_SENT:3>599 <SRX:3>528 <STX:3>665 <TIME_ON:6>211616 <TIME_OFF:6>211616 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:5>31578 <FREQ_RX:9>28 .094200 <EOR>

... to ...

    <APP_LOGGER32_CREDIT_GRANTED:39>LOTW_DXCC,LOTW_DXCC_MIXED ,LOTW_DXCC_CW, <CREDIT_GRANTED:23>DXCC,DXCC_MIXED,DXCC_CW <BAND:3>10M <CALL:4>TF3Y <CONT:2>EU <CONTEST_ID:8>ARRL 10m <CQZ:2>40 <DXCC:3>242 <FREQ:9>28.094200 <GRIDSQUARE:6>HP94bd <IOTA:6>EU-021 <ITUZ:2>17 <MODE:2>CW <OPERATOR:4>ZM4G <PFX:3>TF3 <QSO_DATE:8:D>20111210 <RST_RCVD:3>599 <RST_SENT:3>599 <SRX:3>528 <STX:3>665 <TIME_ON:6>211616 <TIME_OFF:6>211616 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:5>31578 <FREQ_RX:9>28 .094200 <EOR>

The text in bold has been prepended to the record.  The utility adds both <CREDIT_GRANTED> and <APP_LOGGER32_CREDIT_GRANTED> fields because Logger32 uses the additional information about whether the QSO was credited as a result of a QSL card or a LoTW match.

The utility does some integrity checking along the way, generating a plain text error file with information on any credited QSOs it didn’t find in your log - nine QSOs in my case:

DXCC credits downloader errors

HS0ZEA, for example, is the call credited in my DXCC records but in fact he was mobile, and I logged him as HS0ZEA/M (which is the callsign he used on air).  LoTW evidently strips off the /M suffix, giving a mismatch with the QSO in my log.  It is easy to fix these nine errors: I will simply have to edit my log manually to show that these QSOs have been credited for DXCC.

First, though, I must import the ADIF file containing the credits into Logger32: there may be a function in Logger32 to import and synchronize the amended ADIF into my log, but I prefer to create a new logbook and import the amended ADIF there.

So far, Logger32’s the DXCC report has gone from looking like this:

DXCC credits before

with a number of pink G (= Granted) blobs that I had entered previously ... to this:

DXCC credits after

with extra pink G blobs as expected.  However, I noticed that one pink G blob (right hand blob on the second row) has now reverted to a plan orange C (Confirmed) blob.  How odd!

Digging a little deeper, I find that it is a QSO with 4L Georgia on 40m, specifically 4L2M.  He has confirmed the QSO on LoTW and it has been credited to my DXCC record: 

LoTW 4L2M record

The QSO is correctly listed in the ADIF file containing the credits as follows:

    <APP_LOGGER32_CREDIT_GRANTED:39>LOTW_DXCC,LOTW_DXCC_MIXED ,LOTW_DXCC_CW, <CREDIT_GRANTED:24>DXCC,DXCC_MIXED,DXCC_CW, <BAND:3>40M <CALL:4>4L2M <CONT:2>AS <CQZ:2>21   <DXCC:2>75 <FREQ:8>7.026600 <ITUZ:2>29 <MODE:2>CW <OPERATOR:6>ZL2IFB <PFX:3>4L2 <QSL_RCVD:1>Y <QSLRDATE:8>20070331 <QSO_DATE:8:D>20061126 <RST_RCVD:3>599 <RST_SENT:3>599 <TIME_ON:6>053800 <TIME_OFF:6>053800 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:4>1489 <EOR>

It appears Logger32 failed to register the credit when importing that QSO for some unknown reason.  Could be a bug in the statistics function (there are others!).  Anyway, the usual stats recalc fixed it:

DXCC credits after recalc

If you use “ARRL scraper.exe”, it automatically updates your log in Logger32 for you - I think.

So that’s it.  A way to update your DXCC records to GRANTED status using LoTW and Logger32.

Back to quick links


LoTW users

Robert HB9BZA maintains a handy list of LoTW users compiled from “lotwreport.adi” files submitted by those of us who like to help.  The cluster user program by VE7CC uses the list, adding a “+” to the comments field on spots for DX stations who use LoTW.  If two or more wanted DX stations are spotted, I give preference to those with the plusses because I’m more confident of getting a QSL from them.

ARRL, unfortunately, does not release this information directly so it relies upon those lotwreport files to identify who is QSLing via LotW.  If you use LoTW, please send your lotwreport.adi files to HB9BZA every so often (maybe every 500 to 1,000 LoTW QSLs) and help maintain the list.

If you send your lotwreport to Robert, he kindly responds by emailing you back with a list of any new callsigns he’s added to the list.

Back to quick links


Getting help on Logbook of The World (LoTW)

The web page you are reading is “unofficial”, just a compilation of things I have found out while using LoTW. 

Before you log-in to the LoTW system, there is a help and FAQ file by ARRL - not exactly the most helpful source of information. 

If you have other queries not answered in this FAQ or the ARRL files, you could try asking me but you are likely to get a more accurate response from the nice people at ARRL HQ (e.g. try Bill Moore NC1L for DXCC or WAS queries), or by joining the LoTW email reflector at Yahoo!.

Back to quick links


A LoTW wishlist

Here are some changes to LoTW I’d quite like ARRL to make:

  1. Better online help for users who have logged-in to LoTW.  The current online help is useful but is only available from the main LoTW page before you login to LoTW.  Logged-in users are left to flounder around helplessly, as it were.  [ARRL is planning to redevelop the LoTW site and have promised more help.  We are waiting very patiently.]
     
  2. Add more awards such as IOTA and contests such as CQ WW.  ARRL would do us all a service by opening up the system for awards other than DXCC, WAS and WPX, and for contests.  At the very least, this would encourage many more hams to use LoTW.   A relatively simple option would be for LoTW to verify, sign and return submitted ADIF or Cabrillo logs , identifying which of the QSOs have been matched.  Making use of ARRL’s investment in the PKI, LoTW could digitally sign its reports, assuring others that they have not been tampered with.  They would then be able to use the reports for all manner of awards and contests without ARRL having to cater for each one individually.
     
  3. More feedback on the status of award applications.   It would reduce the stress if we knew that our DXCC, WAS or WPX applications were progressing e.g. moving gradually along the queue, awaiting card confirmations, awaiting final checks or whatever.  Given that the checking process is largely automated, status updates could presumably be generated automagically too ...

Please contact me if there are other ideas you would like to add to the list, or to comment on my suggestions. 

Notwithstanding my little wish-list, I’d like to thank ARRL and the DXCC desk for making this facility available to hams worldwide.  Thanks!

Back to quick links

Hawke’s Bay
North Island
New Zealand

39o 39’ South x 176o 37’ East

Locator RF80HL

260m ASL

IOTA OC-036

CQ zone 32

A1 Ops
ARRL
CDXC
FOC
G0FBB
G-QRP-C
M6T
NZART
Voodudes
ZL6QH
ZM4T

DX CoC logo new 125 on black