First Domain Entry Errors as “Invalid Domain Name” on Windows Command Line

[OrlandoMD]

Description

First, thank you — DSS has been extremely helpful for bulk checking domains!

After updating to DSS v3.0.18 on Windows, I observed that when analyzing lists of input domains via command line redirection, the first domain in the list always errors as “invalid domain name.” All subsequent domains process normally.

Steps to Reproduce

1. Create a CSV file (domainsin.csv) with multiple domains:

   ibm.com
   microsoft.com
   rapid7.com
   

2. Run:

   dss.exe scan < domainsin.csv -fCSV -t240s -n1.1.1.1,8.8.8.8 > results.csv

3. Observe that the first domain (ibm.com) is flagged invalid.

Expected Behavior

All domains in the list should be processed correctly.

Actual Behavior

The first domain is consistently marked as invalid, while the rest process correctly.

Sample Output

ibm.com,,,,,,invalid domain name,
microsoft.com,,v=DKIM1; k=rsa; p=...
rapid7.com,v=BIMI1; l=https://...,v=DMARC1; p=quarantine;...

Workaround

Adding a dummy domain as the first entry avoids the error.

Environment

• OS: Windows (command line)
• Version: DSS v3.0.18

[wolveix]

Hey @OrlandoMD, good to hear from you!

Thanks for reporting this, we'll investigate this ASAP.

[OrlandoMD]

@wolveix You bet, still perodically using to check industry implemention progress.
When runnning a larger set of domains, I've also seen a duplicate final output record that may be related to this issue.
Respectfully,
Orlando