Report for anticheatexpert.com

Report created on: Wed, 12 Mar 2025 03:40:45 GMT

Parent		100
NS		0
SOA		77
MX		95
Mail		93
Web		100

NS Records at Parent Servers

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

ns-open1.qq.com. TTL=172800 [117.135.174.196, 43.129.131.155, 59.36.132.139] [2402:4e00:111:ffe::3]
ns-open2.qq.com. TTL=172800 [170.106.32.61, 182.254.59.163, 49.51.76.94, 61.241.27.10] [240e:e1:aa00:2001::3]
ns-open3.qq.com. TTL=172800 [101.227.161.202, 121.51.167.100, 140.207.180.51, 203.205.220.25, 218.68.91.163] [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.

ns-open1.qq.com. → 43.129.131.155, 59.36.132.139, 117.135.174.196
ns-open2.qq.com. → 61.241.27.10, 182.254.59.163, 170.106.32.61, 49.51.76.94
ns-open3.qq.com. → 121.51.167.100, 203.205.220.25, 218.68.91.163, 101.227.161.202, 140.207.180.51

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.

ns-open1.qq.com. → 2402:4e00:111:ffe::3
ns-open2.qq.com. → 240e:e1:aa00:2001::3
ns-open3.qq.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

Domain SOA Record:

Primary nameserver: ns-tel1.qq.com.
Hostmaster (e-mail): webmaster.qq.com.
Serial: 1559700344
Refresh: 300
Retry: 600
Expire: 86400
Minimum TTL: 86400

Name Servers Agreement on Serial Number

WARNING: We found different serial numbers on your name servers, it's OK if you had modified your zone recently.

101.227.161.202: 1559700344
117.135.174.196: 1559700344
121.51.167.100: 1559700344
140.207.180.51: 1559700344
170.106.32.61: 1559700344
182.254.59.163: 0
203.205.220.25: 1559700344
218.68.91.163: 1559700344
2402:4e00:111:ffe::3: 1559700344
240e:e1:aa00:2001::3: 1559700344
43.129.131.155: 1559700344
49.51.76.94: 1559700344
59.36.132.139: 1559700344
61.241.27.10: 1559700344

Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).

SOA Number Format

NOTICE: Although your serial is valid [1559700344], it's not using recommended serial number format YYYYMMDDnn, where YYYY is four-digit year number, MM is the month, DD is the day and nn is the sequence number in case zone file is updated more than once per day.

SOA Mname

WARNING: Primary name server ns-tel1.qq.com. listed in SOA Record is not found at the parent name servers. The MNAME field defines the Primary Master name server for the zone, this name server should be found in your NS records.

SOA Rname

OK. Contact email for DNS problems is webmaster@qq.com. (webmaster.qq.com.). RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster e-mail for this purpose, but any valid e-mail address can be used.

SOA Refresh

WARNING: Refresh interval is 300. Recommended values [1200 .. 43200] (20 min ... 12 hours). Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.

SOA Retry

OK. Retry interval is 600. Recommended values [120 .. 7200] (2 minutes .. 2 hours). Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.

SOA Expire

WARNING: Expire interval is 86400. Recommended values [604800 .. 1209600] (1 week ... 2 weeks). Expiry defines zone expiration time in seconds after which slave must re-validate zone file, if contacting master fails then slave will stop responding to any queries.

SOA Minimum TTL

OK. Minimum TTL value is 86400. Recommended values [3600 .. 86400] (1 hour ... 1 day). Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves to cache negative responses.

MX Records

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

5 mxbiz1.qq.com. TTL=600
10 mxbiz2.qq.com. TTL=600

Identical MX Records

OK. All name servers returned identical MX records.

Mail Servers Have A Records

OK. Found A records for all mail servers.

mxbiz1.qq.com. → 103.86.78.3, 103.86.78.2
mxbiz2.qq.com. → 103.86.78.5, 103.86.78.4

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.

mxbiz1.qq.com. → ?
mxbiz2.qq.com. → ?

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

Reverse Entries for MX records

WARNING: Found mail servers with inconsistent reverse DNS entries. You should fix them if you are using those servers to send email.

Server	IP	PTR (Reverse)	IPs
mxbiz1.qq.com.	103.86.78.3	?	?
mxbiz1.qq.com.	103.86.78.2	?	?
mxbiz2.qq.com.	103.86.78.5	?	?
mxbiz2.qq.com.	103.86.78.4	?	?

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.

mxbiz1.qq.com.:
```
220 bizmx68.qq.com MX QQ Mail Server
```
mxbiz2.qq.com.:
```
220 bizmx59.qq.com MX QQ Mail Server
```

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

Mail Greeting

NOTICE: I've found differences between mail server host names and greeting host name. The following mail servers claims to be other hosts (reverse DNS checks may be wrong):

mxbiz1.qq.com. → bizmx68.qq.com
mxbiz2.qq.com. → bizmx59.qq.com

Accepts Postmaster Address

OK. All mail servers are accepting emails to postmaster@anticheatexpert.com address:

mxbiz1.qq.com.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 Ok
>> RCPT TO: <postmaster@anticheatexpert.com>
<< 250 Ok

mxbiz2.qq.com.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 Ok
>> RCPT TO: <postmaster@anticheatexpert.com>
<< 250 Ok

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

OK. All mail servers are accepting emails to abuse@anticheatexpert.com address:

mxbiz1.qq.com.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 Ok
>> RCPT TO: <abuse@anticheatexpert.com>
<< 250 Ok

mxbiz2.qq.com.

>> MAIL FROM: <postmaster@dnscheck.pro>
<< 250 Ok
>> RCPT TO: <abuse@anticheatexpert.com>
<< 250 Ok

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

OK. Name servers returned identical TXT records. 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

OK. Found DMARC record:

v=DMARC1;p=quarantine;fo=1;ruf=mailto:smartlink_dmarc_report@proximabeta.com;rua=mailto:smartlink_dmarc_report@proximabeta.com

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

OK. Domain anticheatexpert.com. resolves to:

157.148.33.67

Domain Name IPs are Public

OK. No private IPs found for anticheatexpert.com.. Web servers using private IPs can't be reached from the Internet.

Resolve WWW

OK. Domain www.anticheatexpert.com. resolves to:

157.148.33.67

WWW IPs are Public

OK. No private IPs found for www.anticheatexpert.com.. Web servers using private IPs can't be reached from the Internet.

Report completed in 12.17 seconds.

Recent reports: sunindustries.ro remote-it.ro remote-it.ro elitesearchers.ro jdizajn-ugo.com