Report for cgwpllc.com

Report created on: Thu, 29 May 2025 21:28:19 GMT

Parent		100
NS		0
SOA		0
MX		100
Mail		41
Web		75

NS Records at Parent Servers

We have successfully fetched domain's NS records from parent name server (l.gtld-servers.net.).
Domain NS records:

dns105.register.com. TTL=172800 [162.159.24.117] [NO GLUE6]
dns106.register.com. TTL=172800 [162.159.25.158] [NO GLUE6]

Missing Glue

Test ignored, name servers are located outside of current zone.

Name Servers Have A Records

OK. Found A records for all name servers.

dns105.register.com. → 162.159.24.117
dns106.register.com. → 162.159.25.158

To reach your name servers via IPv4 an A record is needed for each name server.

Name Servers Have AAAA Records

NOTICE: While reading domain NS records at parent name servers, we found name servers without AAAA records.

dns105.register.com. → ?
dns106.register.com. → ?

To reach your name servers via IPv6 an AAAA record is needed for each name server.

NS Records

Could not get NS records from your name servers.

Check SOA Record

Could not get SOA record from your name servers.

MX Records

Your name servers returned 2 MX records. Your MX records sorted by priority (lower numbers have higher priority):

10 west.smtp.mx.exch091.serverdata.net. TTL=7200
20 east.smtp.mx.exch091.serverdata.net. TTL=7200

Identical MX Records

OK. All name servers returned identical MX records.

Mail Servers Have A Records

OK. Found A records for all mail servers.

east.smtp.mx.exch091.serverdata.net. → 64.78.24.70
west.smtp.mx.exch091.serverdata.net. → 199.193.206.123

To reach your mail servers via IPv4 an A record is needed for each mail server.

Mail Servers Have AAAA Records

NOTICE: While reading domain NS records at parent mail servers, we found mail servers without AAAA records.

east.smtp.mx.exch091.serverdata.net. → ?
west.smtp.mx.exch091.serverdata.net. → ?

To reach your mail servers via IPv6 an AAAA record is needed for each mail server.

Reverse Entries for MX records

OK. All mail servers have reverse DNS entries configured correctly.

	Server	IP	PTR (Reverse)	IPs
	west.smtp.mx.exch091.serverdata.net.	199.193.206.123	west.smtp.mx.exch091.serverdata.net.	199.193.206.123
	east.smtp.mx.exch091.serverdata.net.	64.78.24.70	east.smtp.mx.exch091.serverdata.net.	64.78.24.70

All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.

All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Check MX Records for Invalid Chars

OK. No invalid characters found. Name field from MX records should be a valid host name.

Check MX Records IPs are Public

OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.

Check MX Records for Duplicates

OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.

Only Host Names in MX Records

OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.

No CNAME in MX Records

OK. No CNAMEs found in MX records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.

RBL Check

OK. Mail servers IPs are not blacklisted.

Check Google Apps Settings

Test ignored, domain is not using Google Apps.

Connect to Mail Servers

OK. Successfully connected to all mail servers.

east.smtp.mx.exch091.serverdata.net.:

220 east.smtp.mx.exch091.serverdata.net exmx091-va-1-1.serverpod.net Microsoft ESMTP MAIL Service Version: 2.0

west.smtp.mx.exch091.serverdata.net.:

220 west.smtp.mx.exch091.serverdata.net exmx091-co-1-1.serverpod.net Microsoft ESMTP MAIL Service Version: 2.0

To receive emails, mail servers should allow TCP connections on port 25.

Mail Greeting

OK. No differences between mail server host names and greeting host name.

Accepts Postmaster Address

WARNING: Found mail servers which are not accepting emails to postmaster@cgwpllc.com address:

east.smtp.mx.exch091.serverdata.net.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 2.1.0 Ok
>> RCPT TO: <postmaster@cgwpllc.com>
<< 550 5.1.1 <postmaster@cgwpllc.com>: Recipient address rejected: User unknown in relay recipient table

west.smtp.mx.exch091.serverdata.net.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 2.1.0 Ok
>> RCPT TO: <postmaster@cgwpllc.com>
<< 550 5.1.1 <postmaster@cgwpllc.com>: Recipient address rejected: User unknown in relay recipient table

RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster. To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.

Accepts Abuse Address

WARNING: Found mail servers which are not accepting emails to abuse@cgwpllc.com address:

east.smtp.mx.exch091.serverdata.net.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 2.1.0 Ok
>> RCPT TO: <abuse@cgwpllc.com>
<< 550 5.1.1 <abuse@cgwpllc.com>: Recipient address rejected: User unknown in relay recipient table

west.smtp.mx.exch091.serverdata.net.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 2.1.0 Ok
>> RCPT TO: <abuse@cgwpllc.com>
<< 550 5.1.1 <abuse@cgwpllc.com>: Recipient address rejected: User unknown in relay recipient table

Check SPF record

WARNING: Domain doesn't have SPF record. SPF (Sender Policy Framework) record is designed to prevent e-mail spoofing. Typical SPF record would be:
v=spf1 a mx ~all or v=spf1 a mx include:_spf.google.com ~all if you are using Google Apps.

Identical TXT records

No TXT records found. Only SPF records are compared, all name servers should return identical SPF records.

Identical SPF records

No SPF type records found. All name servers should return identical SPF records.

Check DMARC record

FAIL: Domain doesn't have DMARC record.

The DMARC uses DKIM keys published in the DNS or IP addresses specified in the SPF record to authenticate emails to protect domain from fraudulent emails.

You can specify a policy how to deal with emails which fails authentication. A typical policy would be to reject, this applies to the domain and all its subdomains without an explicit policy. The DMARC policy has precedence over SPF policy. If you are more conservative, you can start with quarantine.

Example DMARC record:

v=DMARC1; p=quarantine

The authenticated emails will be delivered in the Inbox and others in the Spam/Junk folder.

Resolve Domain Name

WARNING: Could not resolve domain cgwpllc.com..

Domain Name IPs are Public

Could not resolve cgwpllc.com..

Resolve WWW

WARNING: Could not resolve domain www.cgwpllc.com..

WWW IPs are Public

Could not resolve www.cgwpllc.com..

Report completed in 5.52 seconds.

Recent reports: totalpass.com bmrn.com unionip.tv tudconsult.ro oitavotabelionato.com.br