BUG | phishing domains (active/inactive/invalid) are all empty

[brian91292]

What is the problem you are experiencing?

All three of the phishing website txt files are empty, except for new last hour and new today.

How can we reproduce the problem?

No reproduction steps are required. The files are empty.

Do you have a screenshot?

No response

What did you expect to happen?

I expected the domain txt files to have phishing domains in them, and not be empty.

Is there a workaround?

Not using the phishing database.

Additional context

No response

Log information

No response

[phishing-database-bot]

Verification Required

@brian91292, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:

1. Set a DNS TXT record for the domain(s) listed in this issue with the following details:

   • Record Name: _phishingdb
   • Record Value: antiphish-b6a0190d686a4c2e707e023be9a3a65b562df6da

   Your Verification ID: antiphish-b6a0190d686a4c2e707e023be9a3a65b562df6da

2. Wait for DNS propagation (this may take a few minutes to a few hours).

3. Reply to this issue once the TXT record has been set.

Important Notes

• Verification does not guarantee whitelisting. The Phishing.Database team will review your report after verifying ownership, but the decision to whitelist depends on further investigation and analysis.
• If the record cannot be set or you need alternative methods of verification, please contact us at contact@phish.co.za - preferably from the domain's official email address.

How to Check the TXT Record ?

You can verify that the TXT record is properly set using:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.

[nextwavepublish]

@brian91292 any update? I think this is affecting this issue as well https://github.com/Phishing-Database/phishing/issues/749