Correction - they don't have correct RDNS records
in more details:
[-----[11:57pm]:~:4]> dig txt achem.com
; <<>> DiG 9.3.5-P2 <<>> txt achem.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35048
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION:
;achem.com. IN TXT
;; ANSWER SECTION:
achem.com. 30 IN TXT "v=spf1 mx -all"
This tell me that their outbound mail server is the same as inbound (MX) server
[-----[11:59pm]:~:5]> dig mx achem.com
; <<>> DiG 9.3.5-P2 <<>> mx achem.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43556
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 1
;; QUESTION SECTION:
;achem.com. IN MX
;; ANSWER SECTION:
achem.com. 3469 IN MX 10 mail.achem.com.
;; AUTHORITY SECTION:
achem.com. 172595 IN NS ns3.itsoftware.com.
achem.com. 172595 IN NS ns4.itsoftware.com.
achem.com. 172595 IN NS nsa.itsoftware.com.
;; ADDITIONAL SECTION:
mail.achem.com. 3469 IN A 66.59.245.74
So the mail server IP address is 66.59.245.74
[resolver[12:00am]:~:6]> dig -x 66.59.245.74
; <<>> DiG 9.3.5-P2 <<>> -x 66.59.245.74
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52054
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;74.245.59.66.in-addr.arpa. IN PTR
;; ANSWER SECTION:
74.245.59.66.in-addr.arpa. 172800 IN PTR webmail.itsoftware.com.
The reverse lookup for 66.59.245.74 points to webmail.itsoftware.com which is no match to achem.com