You are here: Home > DNS Reports > semutkecil.com

DNS Report for semutkecil.com

Parent
100
NS
51
SOA
94
MX
55
Mail
100
Web
100
B
Parent Status Message
NS Records at Parent Servers info We have successfully fetched domain's NS records from parent name server (j.gtld-servers.net.).
Domain NS records:
  • ns1.cloudns.net. TTL=172800 [85.159.233.17] [2a00:1768:1001:9::1]
  • ns2.cloudns.net. TTL=172800 [108.59.1.205] [2604:9a00:2100:a001:2::1]
  • ns3.cloudns.net. TTL=172800 [109.163.232.165] [NO GLUE6]
  • ns4.cloudns.net. TTL=172800 [85.25.34.84] [NO GLUE6]
  • pns1.cloudns.net. TTL=172800 [87.117.196.78] [NO GLUE6]
  • pns2.cloudns.net. TTL=172800 [186.2.167.49] [NO GLUE6]
  • pns3.cloudns.net. TTL=172800 [72.20.55.83] [NO GLUE6]
  • pns4.cloudns.net. TTL=172800 [109.163.232.239] [NO GLUE6]
  • pns5.cloudns.net. TTL=172800 [190.115.26.18] [NO GLUE6]
  • pns6.cloudns.net. TTL=172800 [64.182.125.213] [NO GLUE6]
  • pns7.cloudns.net. TTL=172800 [NO GLUE4] [NO GLUE6]
  • pns8.cloudns.net. TTL=172800 [NO GLUE4] [NO GLUE6]
  • pns9.cloudns.net. TTL=172800 [NO GLUE4] [NO GLUE6]
Missing Glue skip Test ignored, name servers are located outside of current zone.
Name Servers Have A Records pass OK. Found A records for all name servers.
  • Netherlands ns1.cloudns.net. → 85.159.233.17
  • United States ns2.cloudns.net. → 108.59.1.205
  • Russian Federation ns3.cloudns.net. → 109.163.232.165
  • Germany ns4.cloudns.net. → 85.25.34.84
  • United Kingdom pns1.cloudns.net. → 87.117.196.78
  • -- pns2.cloudns.net. → 186.2.167.49
  • Turkey pns3.cloudns.net. → 72.20.55.83
  • Russian Federation pns4.cloudns.net. → 109.163.232.239
  • -- pns5.cloudns.net. → 190.115.26.18
  • United States pns6.cloudns.net. → 64.182.125.213
  • Canada pns7.cloudns.net. → 67.212.93.178
  • China pns8.cloudns.net. → 119.81.7.18
  • -- pns9.cloudns.net. → 103.18.41.39
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records notice NOTICE: While reading domain NS records at parent name servers, we found name servers without AAAA records.
  • ns1.cloudns.net. → 2a00:1768:1001:9::1
  • ns2.cloudns.net. → 2604:9a00:2100:a001:2::1
  • ns3.cloudns.net. → ?
  • ns4.cloudns.net. → ?
  • pns1.cloudns.net. → ?
  • pns2.cloudns.net. → ?
  • pns3.cloudns.net. → ?
  • pns4.cloudns.net. → ?
  • pns5.cloudns.net. → ?
  • pns6.cloudns.net. → ?
  • pns7.cloudns.net. → ?
  • pns8.cloudns.net. → 2401:c900:1101:de::2
  • pns9.cloudns.net. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
NS Status Message
NS Records info Your name servers returned 13 NS records:
  • ns1.cloudns.net. TTL=3600 [85.159.233.17] [2a00:1768:1001:9::1]
  • ns2.cloudns.net. TTL=3600 [108.59.1.205] [2604:9a00:2100:a001:2::1]
  • ns3.cloudns.net. TTL=3600 [109.163.232.165] [NO GLUE6]
  • ns4.cloudns.net. TTL=3600 [85.25.34.84] [NO GLUE6]
  • pns1.cloudns.net. TTL=3600 [87.117.196.78] [NO GLUE6]
  • pns2.cloudns.net. TTL=3600 [186.2.167.49] [NO GLUE6]
  • pns3.cloudns.net. TTL=3600 [72.20.55.83] [NO GLUE6]
  • pns4.cloudns.net. TTL=3600 [109.163.232.239] [NO GLUE6]
  • pns5.cloudns.net. TTL=3600 [190.115.26.18] [NO GLUE6]
  • pns6.cloudns.net. TTL=3600 [64.182.125.213] [NO GLUE6]
  • pns7.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
  • pns8.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
  • pns9.cloudns.net. TTL=3600 [NO GLUE4] [NO GLUE6]
All Name Servers Responded fail FAIL: While quering domain's records, some of your name servers didn't responded. Name servers which didn't responded:
  • udp4:186.2.167.49
  • udp4:190.115.26.18
Glue Check pass OK. No differences found. The glue provided by the parent name servers has to match the data provided by the authoritative name servers.
Allow Recursive Queries warn WARNING: The following name servers announces themselves as open DNS servers:
  • udp4:186.2.167.49
  • udp4:190.115.26.18
On all name servers which acts as caching name servers recursive queries should be restricted to local networks. Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks. Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic, email and other traffic to malicious hosts compromising security.
Check Name Servers Count pass OK. Domain has 13 name servers. Recommended number, between 2 and 7 name servers (RFC 2182 recommends to have at least 3 authoritative name servers for domains).
Identical NS Records pass OK. All your name servers reported identical NS records. Each name server should return identical NS records.
Check for Lame Name servers warn WARNING: We found name servers which are not authoritative for your domain. Lame name servers:
  • udp4:186.2.167.49
  • udp4:190.115.26.18
All of your name server should be configured either as master or slave for your domain, if a NS records points to a name server that does not answer authoritatively, name server is called lame name server.
Check All IPs are Public pass OK. No private IPs found. Name servers using private IPs can't be reached from the Internet causing DNS delays.
Name Servers Have A Records pass OK. Found A records for each name servers.
  • Netherlands ns1.cloudns.net. → 85.159.233.17
  • United States ns2.cloudns.net. → 108.59.1.205
  • Russian Federation ns3.cloudns.net. → 109.163.232.165
  • Germany ns4.cloudns.net. → 85.25.34.84
  • United Kingdom pns1.cloudns.net. → 87.117.196.78
  • -- pns2.cloudns.net. → 186.2.167.49
  • Turkey pns3.cloudns.net. → 72.20.55.83
  • Russian Federation pns4.cloudns.net. → 109.163.232.239
  • -- pns5.cloudns.net. → 190.115.26.18
  • United States pns6.cloudns.net. → 64.182.125.213
  • Canada pns7.cloudns.net. → 67.212.93.178
  • China pns8.cloudns.net. → 119.81.7.18
  • -- pns9.cloudns.net. → 103.18.41.39
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records notice NOTICE: We found name servers without AAAA records.
  • ns1.cloudns.net. → 2a00:1768:1001:9::1
  • ns2.cloudns.net. → 2604:9a00:2100:a001:2::1
  • ns3.cloudns.net. → ?
  • ns4.cloudns.net. → ?
  • pns1.cloudns.net. → ?
  • pns2.cloudns.net. → ?
  • pns3.cloudns.net. → ?
  • pns4.cloudns.net. → ?
  • pns5.cloudns.net. → ?
  • pns6.cloudns.net. → ?
  • pns7.cloudns.net. → ?
  • pns8.cloudns.net. → 2401:c900:1101:de::2
  • pns9.cloudns.net. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Name Servers Have Valid Names pass OK. All names are valid. Name server name should be a valid host name, no partial name or IP address.
Check for Stealth Name Servers pass OK. No stealth name servers found. All name servers returned by domain name servers should be listed at parent servers.
Check for Missing Name Servers pass OK. No missing name servers found. All name servers returned by the parent name servers should have an NS record at your name servers.
No CNAME in NS Records pass OK. No CNAMEs found in NS 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.
Allow TCP connections warn WARNING: Couldn't connect using TCP protocol:
  • tcp4:190.115.26.18
  • tcp4:64.182.125.213
  • tcp4:87.117.196.78
  • tcp4:186.2.167.49
  • tcp4:72.20.55.83
Check your name server's configurations and firewall rules. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).
Name Servers Distributed on Multiple Networks pass OK. Name servers are dispersed on 12 different C class networks:
  • 103.18.41.0/24:
    • pns9.cloudns.net.
  • 108.59.1.0/24:
    • ns2.cloudns.net.
  • 109.163.232.0/24:
    • ns3.cloudns.net.
    • pns4.cloudns.net.
  • 119.81.7.0/24:
    • pns8.cloudns.net.
  • 186.2.167.0/24:
    • pns2.cloudns.net.
  • 190.115.26.0/24:
    • pns5.cloudns.net.
  • 64.182.125.0/24:
    • pns6.cloudns.net.
  • 67.212.93.0/24:
    • pns7.cloudns.net.
  • 72.20.55.0/24:
    • pns3.cloudns.net.
  • 85.159.233.0/24:
    • ns1.cloudns.net.
  • 85.25.34.0/24:
    • ns4.cloudns.net.
  • 87.117.196.0/24:
    • pns1.cloudns.net.
Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Distributed on Multiple ASNs pass OK. Name servers are dispersed on 11 different Autonomous Systems:
  • AS8972:
    • ns4.cloudns.net.
  • AS10929:
    • pns7.cloudns.net.
  • AS20860:
    • pns1.cloudns.net.
  • AS25761:
    • pns3.cloudns.net.
  • AS30633:
    • ns2.cloudns.net.
  • AS36351:
    • pns8.cloudns.net.
  • AS39743:
    • ns3.cloudns.net.
    • pns4.cloudns.net.
  • AS43350:
    • ns1.cloudns.net.
  • AS54489:
    • pns6.cloudns.net.
  • AS58940:
    • pns9.cloudns.net.
  • AS262254:
    • pns2.cloudns.net.
    • pns5.cloudns.net.
Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Versions pass OK. Name servers software versions are not exposed:
  • 103.18.41.39: "unknown"
  • 108.59.1.205: "unknown"
  • 109.163.232.165: "unknown"
  • 109.163.232.239: "unknown"
  • 119.81.7.18: "unknown"
  • 186.2.167.49: "unknown"
  • 190.115.26.18: "unknown"
  • 2401:c900:1101:de::2: "unknown"
  • 2604:9a00:2100:a001:2::1: "unknown"
  • 2a00:1768:1001:9::1: "unknown"
  • 64.182.125.213: "unknown"
  • 67.212.93.178: "unknown"
  • 72.20.55.83: "unknown"
  • 85.159.233.17: "unknown"
  • 85.25.34.84: "unknown"
  • 87.117.196.78: "unknown"
Exposing name server's versions may be risky, when a new vulnerability is found your name servers may be automatically exploited by script kiddies until you patch the system. Learn how to hide version.
SOA Status Message
Check SOA Record info Domain SOA Record:
  • Primary nameserver: pns7.cloudns.net.
  • Hostmaster (e-mail): support.cloudns.net.
  • Serial: 2014121309
  • Refresh: 7200
  • Retry: 1800
  • Expire: 1209600
  • Minimum TTL: 3600
Name Servers Agreement on Serial Number warn WARNING: We found different serial numbers on your name servers, it's OK if you had modified your zone recently.
  • 103.18.41.39: 2014121309
  • 108.59.1.205: 2014121309
  • 109.163.232.165: 2014121309
  • 109.163.232.239: 2014121309
  • 119.81.7.18: 2014121309
  • 186.2.167.49: 0
  • 190.115.26.18: 0
  • 2401:c900:1101:de::2: 2014121309
  • 2604:9a00:2100:a001:2::1: 2014121309
  • 2a00:1768:1001:9::1: 2014121309
  • 64.182.125.213: 2014121309
  • 67.212.93.178: 2014121309
  • 72.20.55.83: 2014121309
  • 85.159.233.17: 2014121309
  • 85.25.34.84: 2014121309
  • 87.117.196.78: 2014121309
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 pass OK. Serial number format OK [2014121309]. Your serial number is following general convention for serial number 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 pass OK. Primary name server is pns7.cloudns.net. and is listed 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 pass OK. Contact email for DNS problems is support@cloudns.net. (support.cloudns.net.). 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 pass OK. Refresh interval is 7200. 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 pass OK. Retry interval is 1800. 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 pass OK. Expire interval is 1209600. 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 pass OK. Minimum TTL value is 3600. 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 Status Message
MX Records info Your name servers returned 2 MX records:
  • 10 mailforward2.cloudns.net. TTL=3600
  • 10 mailforward1.cloudns.net. TTL=3600
Identical MX Records fail FAIL: Name servers reported different MX records:
  • 103.18.41.39: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 108.59.1.205: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 109.163.232.165: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 109.163.232.239: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 119.81.7.18: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 186.2.167.49: []
  • 190.115.26.18: []
  • 64.182.125.213: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 67.212.93.178: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 72.20.55.83: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 85.159.233.17: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 85.25.34.84: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
  • 87.117.196.78: [mailforward1.cloudns.net. mailforward2.cloudns.net.]
Mail Servers Have A Records pass OK. Found A records for all mail servers.
  • United States mailforward1.cloudns.net. → 108.59.1.247, 85.159.233.30
  • United States mailforward2.cloudns.net. → 108.59.5.204
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records pass OK. Found AAAA records for all mail servers.
  • mailforward1.cloudns.net. → 2604:9a00:2100:a008:7::2, 2604:9a00:2100:a001:2::2
  • mailforward2.cloudns.net. → 2604:9a00:2100:a000:3::3, 2604:9a00:2100:a000:3::2
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records warn 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
mailforward2.cloudns.net. 108.59.5.204 mailforward2.cloudns.net. 108.59.5.204
mailforward1.cloudns.net. 108.59.1.247 mailforward1.cloudns.net. 85.159.233.30, 108.59.1.247
mailforward1.cloudns.net. 85.159.233.30 mailforward1.cloudns.net. 85.159.233.30, 108.59.1.247
mailforward2.cloudns.net. 2604:9a00:2100:a000:3::3 ? ?
mailforward2.cloudns.net. 2604:9a00:2100:a000:3::2 ? ?
mailforward1.cloudns.net. 2604:9a00:2100:a008:7::2 mailforward1.cloudns.net. 2604:9a00:2100:a001:2::2, 2604:9a00:2100:a008:7::2
mailforward1.cloudns.net. 2604:9a00:2100:a001:2::2 mailforward1.cloudns.net. 2604:9a00:2100:a001:2::2, 2604:9a00:2100:a008:7::2

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 pass OK. No invalid characters found. Name field from MX records should be a valid host name.
Check MX Records IPs are Public pass 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 pass 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 pass OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.
No CNAME in MX Records pass 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 pass OK. Mail servers IPs are not blacklisted.
Check Google Apps Settings skip Test ignored, domain is not using Google Apps.
Mail Status Message
Connect to Mail Servers pass OK. Successfully connected to all mail servers.
  • mailforward1.cloudns.net.:
    220 mailforward1.cloudns.net ESMTP (ClouDNS.net mail forwarding service)
  • mailforward2.cloudns.net.:
    220 mailforward2.cloudns.net ESMTP (ClouDNS.net mail forwarding service)
To receive emails, mail servers should allow TCP connections on port 25.
Mail Greeting pass OK. No differences between mail server host names and greeting host name.
Accepts Postmaster Address pass OK. All mail servers are accepting emails to postmaster@semutkecil.com address:
  • mailforward1.cloudns.net.
    >> MAIL FROM: <dnsreport@dnsinspect.com>
    << 250 2.1.0 Ok
    >> RCPT TO: <postmaster@semutkecil.com>
    << 250 2.1.5 Ok
    
  • mailforward2.cloudns.net.
    >> MAIL FROM: <dnsreport@dnsinspect.com>
    << 250 2.1.0 Ok
    >> RCPT TO: <postmaster@semutkecil.com>
    << 250 2.1.5 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 pass OK. All mail servers are accepting emails to abuse@semutkecil.com address:
  • mailforward1.cloudns.net.
    >> MAIL FROM: <dnsreport@dnsinspect.com>
    << 250 2.1.0 Ok
    >> RCPT TO: <abuse@semutkecil.com>
    << 250 2.1.5 Ok
    
  • mailforward2.cloudns.net.
    >> MAIL FROM: <dnsreport@dnsinspect.com>
    << 250 2.1.0 Ok
    >> RCPT TO: <abuse@semutkecil.com>
    << 250 2.1.5 Ok
    
Check SPF record pass OK. Found SPF record:
  • v=spf1 +a +mx -all
SPF (Sender Policy Framework) record is designed to prevent e-mail SPAM. 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 pass OK. Name servers returned identical TXT records. Only SPF records are compared, all name servers should return identical SPF records.
Identical SPF records pass OK. Name servers returned identical SPF records. All name servers should return identical SPF records.
Check DMARC record notice NOTICE: Domain doesn't have DMARC record. DMARC (Domain-based Message Authentication, Reporting & Conformance) helps reducing potential of email-based abuse such as spam and phishing e-mails.
Web Status Message
Resolve Domain Name pass OK. Domain semutkecil.com. resolves to:
  • -- 5.254.113.29
Domain Name IPs are Public pass OK. No private IPs found for semutkecil.com.. Web servers using private IPs can't be reached from the Internet.
Resolve WWW pass OK. Domain www.semutkecil.com. resolves to:
  • -- 5.254.113.29
WWW IPs are Public pass OK. No private IPs found for www.semutkecil.com.. Web servers using private IPs can't be reached from the Internet.

Report completed in 13.70 seconds.

Recent reports: kerdos.gr viu.ca d3co.net yocambiovalencia.es viu.ca

DNS Hosting by LuaDNS
Powered by Go & Jekyll