Home

Awesome

<h1 align="center"> <br> <a href=" https://github.com/BLACK-SCORP10/Email-Vulnerablity-Checker.git"><img src="img/EVC.png"></a> <br> Email Vulnerability Checker v2.1 <br> </h1> <p align="center">Verify whether the domain is vulnerable to spoofing by Email-vulnerablity-checker</p>

Features of Version 2.1

Email Vulnerability Checker

This script checks the SPF and DMARC configurations of email domains to determine their vulnerability status. It's useful for system administrators or security professionals to assess email infrastructure security.

Usage

To run the script, execute it with the following command:

./spfvuln.sh [options]

Options

Requirements

Installation Steps

  1. Clone the Repository:

    git clone https://github.com/BLACK-SCORP10/Email-Vulnerability-Checker.git
    
  2. Navigate to the Directory:

    cd Email-Vulnerability-Checker
    
  3. Make the Script Executable:

    chmod +x spfvuln.sh
    
  4. Install Requirements:

    For Ubuntu or Debian:

    sudo apt update
    sudo apt install dnsutils
    

    For CentOS or RHEL:

    sudo yum install bind-utils   # CentOS, RHEL
    

    or

    sudo dnf install bind-utils   # Fedora
    
  5. Verify Installation:

    nslookup example.com
    

    or

    nslookup -version
    

Usage

Example Usage

Checking a single domain:

./spfvuln.sh -d example.com

Checking multiple domains from a file:

./spfvuln.sh -t domains.txt

Saving results to an output file:

./spfvuln.sh -d example.com -o output.txt

Updating the tool

To update your tool after a new version has been released, follow these steps:

  1. Navigate to the Tool Directory:

    cd Email-Vulnerability-Checker
    
  2. Pull the Latest Changes from the Remote Repository:

    git pull origin main
    

Notes

Preview

<a href=" https://github.com/BLACK-SCORP10/Email-Vulnerablity-Checker.git"><img src="img/image.png"></a>

Detail Description On Configurations Flag

SPF ConfigurationDMARC ConfigurationVulnerability StatusExplanation
-allRejectNot VulnerableSPF (-all) with DMARC reject policy ensures that unauthorized emails are rejected outright, minimizing spoofing risks.
-allQuarantineLess VulnerableSPF (-all) with DMARC quarantine policy sends unauthorized emails to spam or a designated folder, reducing risks.
-allNoneVulnerableSPF (-all) without DMARC leaves some vulnerability, as DMARC can enhance email authentication and alignment.
-allNo AnswerVulnerableThe presence of "redirect" or other mechanisms not explicitly defined can lead to vulnerabilities, depending on the redirected domain's SPF configuration.
~allRejectLess VulnerableSPF soft fail (~all) with DMARC reject policy may allow unauthorized emails but rejects those failing DMARC alignment.
~allQuarantineMore VulnerableSPF soft fail (~all) with DMARC quarantine policy may allow unauthorized emails but sends them to spam or a designated folder.
~allNoneVulnerableSPF soft fail (~all) without DMARC leaves more vulnerability, as DMARC can enhance email authentication and alignment.
~allNo AnswerVulnerableThe presence of "redirect" or other mechanisms not explicitly defined can lead to vulnerabilities, depending on the redirected domain's SPF configuration.
+allRejectVulnerableSPF pass (+all) with DMARC reject policy is vulnerable as it accepts all emails without proper authentication or alignment.
+allQuarantineMore VulnerableSPF pass (+all) with DMARC quarantine policy may allow all emails but sends unauthorized ones to spam or a designated folder.
+allNoneVulnerableSPF pass (+all) without DMARC leaves vulnerability, as DMARC can enhance email authentication and alignment.
+allNo AnswerVulnerableThe presence of "redirect" or other mechanisms not explicitly defined can lead to vulnerabilities, depending on the redirected domain's SPF configuration.
?allRejectVulnerableSPF neutral (?all) with DMARC reject policy doesn't provide strong protection, potentially allowing unauthorized emails.
?allQuarantineMore VulnerableSPF neutral (?all) with DMARC quarantine policy may allow unauthorized emails but sends them to spam or a designated folder.
?allNoneVulnerableSPF neutral (?all) without DMARC leaves vulnerability, as DMARC can enhance email authentication and alignment.
?allNo AnswerVulnerableThe presence of "redirect" or other mechanisms not explicitly defined can lead to vulnerabilities, depending on the redirected domain's SPF configuration.
N/ARejectVulnerableWithout SPF, DMARC reject policy doesn't provide strong protection against unauthorized emails, potentially allowing spoofing and phishing.
N/AQuarantineMore VulnerableWithout SPF, DMARC quarantine policy may allow unauthorized emails but sends them to spam or a designated folder.
N/ANoneHighly VulnerableWithout SPF, DMARC none policy leaves the domain highly vulnerable to various email-based threats, including spoofing and phishing attacks.
N/ANo AnswerHighly VulnerableThe absence of both SPF and DMARC records leaves the domain highly vulnerable to various email-based threats, including spoofing and phishing attacks, especially if "redirect" or other mechanisms not explicitly defined are present.

Other types are Redirect Mechanism and Multiple SPF Flags.

Author

This Email Vulnerability Checker script was created by BLACK-SCORP10. For queries or feedback, contact the author via Telegram: BLACK-SCORP10.

Version

Current version: 2.1

Disclaimer

This script is provided as-is, Use it at your own risk.

Support

For Queries: Telegram
Contributions, issues, and feature requests are welcome!
Give a ★ if you like this project!

License

This project is licensed under the MIT License - see the LICENSE file for details.