Phishing | example.com

[Igor4er]

What are the subjects of the phishing (domains, URLs or IPs)?

• example.com
• sub.example.com
• https://example.com/page
• https://sub.example.com/page
• NSFW example.com
• 192.168.0.0/16

What are the impersonated domains?

• example.org
• sub.example.org
• https://example.org/page
• https://sub.example.org/page

Where or how did you discover this phishing?

I discovered this phishing by...
I was targeted by this phishing by...

Do you have a screenshot?

Screenshot

Related external source

• https://sub.example.co.uk/page

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@Igor4er, 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-b333f684c5366c496e07acc8ca19eee3c6231206

   Your Verification ID: antiphish-b333f684c5366c496e07acc8ca19eee3c6231206

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.