mxtoolbox | IP address on very known spam databases | Email library

by heximcz PHP Version: 0.1.1 License: Non-SPDX

X-Ray Key Features Code Snippets(1)Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | mxtoolbox Summary

mxtoolbox is a PHP library typically used in Messaging, Email applications. mxtoolbox has no bugs, it has no vulnerabilities and it has low support. However mxtoolbox has a Non-SPDX License. You can download it from GitHub.

MxToolBox - test your IP address on very known spam databases and blacklists

Support

Quality

Security

License

Reuse

Support

mxtoolbox has a low active ecosystem.

It has 14 star(s) with 8 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 2 have been closed. On average issues are closed in 4 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of mxtoolbox is 0.1.1

Quality

mxtoolbox has 0 bugs and 0 code smells.

Security

mxtoolbox has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mxtoolbox code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mxtoolbox has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

mxtoolbox releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 1234 lines of code, 98 functions and 26 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed mxtoolbox and discovered the below as its top functions. This is intended to give you an instant insight into mxtoolbox implemented functionality, and help decide if they suit your requirements.

Get Digip from Digip
Create the blacklisted file
Check all DNS blanks .
Parse SMTP results
Load blacklists from file
Set final results array
Parse the digroc data from the multiproc .
Check if an IP address exists
Set test result array
Remove previous results array .

Get all kandi verified functions for this library.

mxtoolbox Key Features

No Key Features are available at this moment for mxtoolbox.

mxtoolbox Examples and Code Snippets

MXToolbox,Installation / Usage

PHP

Lines of Code : 64

License : Non-SPDX (NOASSERTION)

Copy

    composer require mxtoolbox/mxtoolbox    

    {
    "require": {
        "mxtoolbox/mxtoolbox": ">=0.0.1"
        }
    }

setDig('/usr/bin/dig')
        // set dns resolver - required
        //->setDnsResolver('8.8.8.8')
        //->se

Community Discussions

Trending Discussions on mxtoolbox

DigitalOcean A records and CNAMEs not propogating?

Primary Name Server Not Listed At Parent

SMTP Reverse DNS Mismatch issue

Best Practice DNS Configuration for Single Server Hosting Multiple Domains

Spf Records Prevent "Too Many MX Resource Records" and too many operators / remove duplicate actions

SendGrid smtp not sending to Yahoo, AOL, or Verizon.net but sends to Gmail?

DNS when hosting a static website on Google Cloud Platform bucket

AWS SES - Are IP Addresses used for multiple accounts or are they unique to me? Hit a Spam Trap for an email I didn't send

PHPMailer Can't Connect, but off-server SMTP testing tool works

MXToolbox reports "Too Many MX Lookups" on my SPF record but I can't see why. What am I missing?

QUESTION

DigitalOcean A records and CNAMEs not propogating?

Asked 2021-Nov-16 at 22:49

I am having some issues with DigitalOcean A records and CNAMEs. An A record for www.schoolproject.me was created, and DO would not let me make one for just schoolproject.me (do I need to make one for @.schoolproject.me instead?).

When checking both of those domain names for A records on either MXToolbox or a propagation checker, neither of them provide any response whatsoever. For subdomains of this, I have CNAMEs done in DO as well (this is an Evilginx project, so ones for api.twitter.com.schoolproject.me, abs.twitter.com.schoolproject.me, and twitter.com.schoolproject.me) which also don't have CNAMEs in MXToolbox.

The nameservers were set up in Namecheap, as nsX.schoolproject.me - 1-3 as X that point to the IP of the DO droplet, as suggested in Evilginx setup guides.

The question is, why aren't these A records and CNAMEs showing up in any tool? When Evilginx attempts to get SSL certs from LetsEncrypt I am met with this -

...

ANSWER

Answered 2021-Nov-16 at 22:49

Fixed it. In Namecheap, make sure to add your nameservers you made under Advanced DNS settings to the Custom Nameserver section of the site. Ugh. That was too easy.

Source https://stackoverflow.com/questions/69994491

QUESTION

Primary Name Server Not Listed At Parent

Asked 2021-Mar-07 at 23:59

I have a hosted zone created in Route53 and updated the NS records under the namespaces of the purchased domain.

Unfortunately the DNS check does not return or point to the new NS records instead gets resolved to old/ previously existing records.

I waited more than 72 hours and still i get "This site can’t be reached"failing with error DNS_PROBE_FINISHED_NXDOMAIN in the browser.

Below is a screenshot from the DNS check provided by https://mxtoolbox.com/,

It shows that the old NS records (First 4 rows with TTL to 48 hours) are present in the Parent and not in local whereas the newly updated records (The last 4 records) are present in the parent and not in the local.

Ping to the domain fails with Unknown host.

What are the next steps?

...

ANSWER

Answered 2021-Mar-07 at 23:59

When you update the name servers for a domain, remove the old name server records.

Your TTL is set to 48 hours. That means any recursive resolver such as dns.google will not refresh for 48 hours after last update. For resolvers that have not cached your resource records, they might update immediately but might also get stale data from an upstream resolver. Wait a few hours so that you do not force a new cache load with old data and then check with an Internet tool such as dnschecker.org Change the selection box from A to NS to see the name server changes.

In general I recommend that it takes 48 to 72 hours for authoritative name server changes to propagate around the world.

Google DNS supports "Flush Cache". Wait an hour or two and then request that Google update their DNS cache. Flush Cache

Cloudflare also supports Purge Cache

Google and Cloudflare are very popular DNS resolvers.

Also, do not forget to flush your local computer's DNS cache:

Windows: ipconfig /flushdns
Linux: sudo service network-manager restart (ubuntu) or sudo /etc/init.d/nscd restart
macOS: sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder

Source https://stackoverflow.com/questions/66519744

QUESTION

SMTP Reverse DNS Mismatch issue

Asked 2020-Nov-10 at 23:33

According to MXToolbox my server has a problem.

Please review: https://mxtoolbox.com/SuperTool.aspx?action=smtp%3awebmaus.net&run=toolpage

The tool shows a 'SMTP Reverse DNS Mismatch' and I don't have an idea why. My PTR Records look like:

...

ANSWER

Answered 2020-Nov-10 at 23:33

Reverse DNS: closed PTR-A loop

SMTP servers check "closed loop" of PTR and A records.
IP address -> [ PTR record ] -> Name -> [ A record ] -> IP address
Rogue nets can set PTR to any name they like.

There seems to be no A record for 158.22.202.116.pleiades.webmaus.net.

Source https://stackoverflow.com/questions/64771644

QUESTION

Best Practice DNS Configuration for Single Server Hosting Multiple Domains

Asked 2020-Aug-16 at 19:10

Note: IP addresses and domain names have been changed to equivalents so as not to attract attacks!

Background

I'm setting up a standalone VPS on which I'll host half a dozen or so domains catering both email and web hosting. I may add additional VPSs later but don't want to register a new FQDN for each new server. I plan to have single domain name with a subdomain created for each server. For example s1.myserverdomain.com and s2.myserverdomain.com. These FQDNs will be used to provide resolvable names for common services like mail.s1.myserverdomain.com.

The first VPS will have two IP addresses, so that I can use it for providing nameserver services as ns1.s1.myserverdomain.com and ns2.s1.myserverdomain.com. Later, when I add another server, I'll split them up.

(You might tell me that this is bad practice to run both nameservers on the same machine, because in the event that one goes down, so will the other, but considering that in that instance, so too will the mail and web hosting, there doesn't seem much point paying for another server just yet.)

What I want to finish up with is with godaddy handling the DNS for myserverdomain.com and creation of nameservers for ns1.s1..., ns2.s1... on my VPS and later will transfer ns2.s1 to ns2.s2. I will set the nameservers for each of the half dozen hosted domains to use those nameservers.

My Configuration

So far I have created the following DNS records at Godaddy for myserverdomain.com in addition to the default records created automatically by Godaddy:

...

ANSWER

Answered 2020-Aug-16 at 19:10

Could be several things, maybe you have port 53 closed, maybe your NS records aren't set up correctly, etc...

You already noted how having the nameservers on the same machine is bad practice. Using a second IP is useless, I wouldn't bother. People can point a subdomains to a different IP address, and some DNS providers will wait a long time if they can't reach you, so even if your server is down for a minute, for some users it will be down for a long time.

If you share your domain name, we can look it up and see what's wrong. You can also do this yourself with tools like zonemaster.net and intodns.com

Lastly, ISPConfig has a good forum on howtoforge.com/community, I recommend it!

Source https://stackoverflow.com/questions/63435920

QUESTION

Spf Records Prevent "Too Many MX Resource Records" and too many operators / remove duplicate actions

Asked 2020-Aug-06 at 14:07

we have setup SPF like below (ips changed for demo purposes)

...

ANSWER

Answered 2020-Aug-06 at 14:07

That error is a bit confusing – it doesn't sound like it's about your SPF, but about your MX records.

MX records designate your inbound mail servers, and do not necessarily correspond with the servers that can send for your domain, which is what SPF covers. For example, it's likely your web server can send mail for your domain, but it won't accept mail sent to it.

It does sound like you have too many MX records. Without knowing your domain I can't check that, but you shouldn't have more than about 5.

Aside from that, your SPF looks fine.

Source https://stackoverflow.com/questions/63284961

QUESTION

SendGrid smtp not sending to Yahoo, AOL, or Verizon.net but sends to Gmail?

Asked 2020-Aug-04 at 18:28

(Disclaimer I'm fairly new to development in general and this is my first StackOverflow post all and any feedback is greatly appreciated.)

I'm posting here because I'm on a free SendGrid account and their support team has yet to get back to respond and it's been over a week and I'm dying to solve this issue.

Currently, I'm using Sendgrid as an SMTP and recently my emails have stopped sending to the following esp Yahoo, AOL, and Verizon.net but emails send to Gmail just fine.

Because emails still send to Gmail I used "Email Header Analyzer" via mxtoolbox.com to review and meet the recommendations provided. Which I have implemented on. (See screenshot)

The only thing not checked off is the "DKIM Authenticated" in which it's my understanding that when you verify the domain you're using to send emails with SendGrid takes care of that for you.

It's not the email function itself because it sends just fine to Gmail.

My question is has anyone else experienced this issue? If so what was the fix you did that made it work?

Screenshot of my email header analyzer results:

...

ANSWER

Answered 2020-Aug-04 at 18:28

Turns out that my SendGrid account was over the daily email sending limit for the "free plan" and the emails that were sent correctly to Gmail had been doing so because of a pre-existing mail function (not using SendGrid even though SendGrid was still logging these emails).

I figured out this was happening by looking at the "mailed-by:" info when you toggle the drop-down above the email just under the sender email address. Mailed-ByView With SendGrid it would say "mail-by: sendgird.net" SendGird-Mailed-ByView

It would have been nice if SendGrid made my sending limit information a little more apparent but you can find this information about your account by going to "Settings">"Account Details">"Your Products." YourProductsView

Source https://stackoverflow.com/questions/63197238

QUESTION

DNS when hosting a static website on Google Cloud Platform bucket

Asked 2020-May-08 at 13:59

Sorry if my question may seem messy I have only a basic idea about DNS or hosting. The story is the following:

I have created a couple of my personal webpages and registered a domain. Then I found out that I don't need a "big" hosting for my couple of pages and it's better to host a website in the cloud, I chose GCP for hosting, found this tutorial and followed through to successfully achieve my goal of hosting a static website.

Then I wanted to share a link to my website in social media and found out that Open Graph Protocol meta information I've added to my website is not displaying while the site is working ok. Strange thing, I thought and started searching. I found Facebook debugger tool and used it to check my website only to see the "Could not resolve the hostname into a valid IP address." response.

I searched for more information about that issue and found a StackOverflow question, where it's said something about domain, hosting, and DNS. Basically, I figured out that DNS servers in my domain registrar's panel are configured for the registrar's hosting while I use GCP for hosting. And I need those DNS servers to match for OGP meta info to work properly.

Any research that I dis, lead me to GCP DNS. But I'm not sure that configuring GCP DNS (which is not GCP bucket storage that I use for hosting my static website) is a good idea or the right way to solve my issue.

Do I need to configure GCP DNS, create VM, and host my website there? Or do I need to specify some special GCP DNS servers in my domain registrar's control panel? Or do I need to do something else?

Please, point me in the right direction. I need my website not just to be available on the internet as a hyperlink, I want the OGP metadata to be available and visible when sharing the link in social media. I don't mind if my website will be hosted on a bucket or on VM of GCP DNS, I just want to understand in what direction I should dig.

Details: My domain is http://www.vladimir-markiev.name/. I followed every step of GCP tutorial exactly as described in documentation: enabled billing, verified domain ownership, configured CNAME record at domain registrar's DNS to www. vladimir-markiev.name (that www. in the beginning irritates me a little, maybe I'll try to deal with it later). I managed access to my bucket to "public and can be accessed by anyone on the internet". I can add my own list of DNS servers to my domain - the registrar allows to do that.

Update: Somehow CNAME record was missing from my domain. I configured it to point to GCP. Check successful.

I also ran a DNS check and it gave out some issues:

CNAME www → c.storage.googleapis.com.

But the issue persists.

Ask me any additional questions for clarification, I tried to include as much information as possible but could have missed something

...

ANSWER

Answered 2020-May-08 at 13:59

When I checked DNS records for your domain first time I found that you misconfigured CNAME record:

Source https://stackoverflow.com/questions/61676499

QUESTION

AWS SES - Are IP Addresses used for multiple accounts or are they unique to me? Hit a Spam Trap for an email I didn't send

Asked 2020-Apr-14 at 21:52

Hey so I used MXToolBox ( https://mxtoolbox.com/ ) to check the headers on one of the emails sent from my system and noticed we were blacklisted on SORBS ( http://support.sorbs.net/ ).

I use AWS SES to send emails from our system for Forgot Password, Verify Email etc.

I sent a request to be removed from the blacklist and they accepted my request but said we were caught by a Spam Trap. He gave me an example of the most recent email that was captured by the Spam Trap with Host & Domains hidden.

The subject for the email was "CoronaVirus Update (COVID-19)" and the From field was "From: Raj Rummy". I have never heard of that name and no one in my company sent any emails with that subject.

Is the IP Address that my emails get sent from directly tied to me or are they more generic AWS IP Addresses that can be tied to multiple AWS SES accounts?
If it is directly tied to me how would I go about figuring out how they got access to send emails from my IP Address?

...

ANSWER

Answered 2020-Apr-08 at 20:36

AWS SES will use its own managed set of IP address for e-mail sending. You can however apply for a dedicated (leased) IP address as described here. Extra costs apply as described here.

In order to perform tracing for e-mail sending in AWS SES, you should monitor your sending activity. This will not only allow you to investigate such events but it will allow you to track bounces/complaints effectively and proactively (i.e. raise an alarm when bounce rate is above threshold).

Source https://stackoverflow.com/questions/61107615

QUESTION

PHPMailer Can't Connect, but off-server SMTP testing tool works

Asked 2020-Mar-17 at 14:16

I'm trying to implement a mailer in my PHP website.

Using PHPMailer installed with Composer. I'm on Ubuntu 18.04 LTS on a Linode VPS.

The page takes a very long time to load, then shows the exception.

test.php

...

ANSWER

Answered 2020-Mar-17 at 05:18

Per Linode's user agreement, outbound mail ports are blocked by default. A support ticket later and I'm up and running. If you run into an issue with PHPMailer or SwiftMailer like the above (notably the extreme page load times), then confirm that your hosting provider is not blocking ports 465, 25, and 587.

Source https://stackoverflow.com/questions/60700720

QUESTION

MXToolbox reports "Too Many MX Lookups" on my SPF record but I can't see why. What am I missing?

Asked 2020-Feb-12 at 10:54

A week or so ago, I discovered that MXToolbox was reporting an error when performing an SPF Lookup on my primary email domain abzorb.co.uk.

https://mxtoolbox.com/SuperTool.aspx?action=mx%3aabzorb.co.uk&run=toolpage#

"SPF MX Resource Records - Too Many MX Resource Records(24)"

I have since consolidated all my "include:" references to "ip4:" references but I'm still being flagged as having too many MX resource records.

We use Mimecast and so the domain's two MX records are Mimecast's EU servers.

My current SPF is: v=spf1 a mx ip4:217.16.193.20 ip4:217.16.192.74 ip4:88.215.56.232 ip4:154.51.129.140 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 ip4:91.220.42.0/24 ip4:146.101.78.0/24 ip4:185.58.85.0/24 ip4:185.58.86.0/24 ip4:195.130.217.0/24 ip4:207.82.80.0/24 ip4:213.167.75.0/25 ip4:213.167.81.0/25 ~all

What am I missing? Why am I still being flagged as having too many MX resource records?

...

ANSWER

Answered 2020-Feb-12 at 10:54

There are actually two things to note:

The title from MXToolbox' error is actually quite confusing! The actual error is about the number of A or AAAA records underlying the MX records rather than the number of MX records.
I think that instead of the MX mechanism you would want to use the include mechanism for authorising mimecast servers through SPF.

Error Title

The error title says "Too many MX resource records". Yet the SPF record only specifies one MX mechanism, resulting in two MX records. Which is fine.

The information page you are directed to explains by referencing the RFC for SPF, section 4.6.4:

... your SPF record contains a mx mechanism which has one or more Mail Exchange (MX) resource records that contain more than 10 address records - either "A" or "AAAA" resource records.

In your case, those two MX records resolve to 12 A records each, 24 in total. The RFC for SPF limits the number of A records to 10, further stating:

If this limit is exceeded, the "mx" mechanism MUST produce a "permerror" result.

Use of the MX mechanism

In many cases the use of the MX mechanism (and A mechanism) in SPF records results from copying examples from a 3rd party service documentation, which generally look like v=spf1 a mx include:[3rd party domain] ~all. Quite often the servers configured for receiving email are not the same servers that are used for sending emails outbound. Especially in case of mailbox hosting services (ESPs) and SPAM filtering services, including Mimecast.

In your situation it would make more sense to set up your SPF record as per instructions of Mimecast here. Of course you should also add ip4: mechanisms for additional servers that you wish to authorise to send on your domain's behalf. You may also use include mechanisms but keep in mind the Global Mimecast include mechanism already adds 5 lookups to your count.

Source https://stackoverflow.com/questions/60093822

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mxtoolbox

Via composer
Create a composer.json defining your dependencies.
Example usage:

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: