DNS lookup record results for the domain Do-lan.com

The DNS record types tested in our free DNS domain lookup test are divided into 6 large groups with a total of 71 tests:

  • DNS Parent Group - 5 tests
  • NS (Nameserver) - 17 tests
  • SOA (Start of Authority) - 9 tests
  • MX (Mail Exchanger) - 12 tests
  • MAIL (Email) - 4 tests
  • WWW (World Wide Web) - 24 tests

For ease of summarization, review and understanding, we have divided the test results of our DNS lookup record check in four statuses:

  • PASS status - No problem was found in the DNS record
  • FAIL status - We found a DNS record error that requires your attention
  • WARN status - We found a minor DNS record error
  • INFO status - Only information about a given DNS record for educational purposes without any detected errors



Below is an overview of the record results of our comprehensive DNS lookup check for a domain Do-lan.com:

DNS Group DNS Status DNS Test Name DNS Record Information
PARENT
PASS Missing Direct Parent check OK. Your direct parent zone exists, SOA of parent zone com is a.gtld-servers.net which is good. Some domains (usually third or fourth level domains, such as example.co.us or subdomain.example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
FAIL Glue at parent nameservers The parent servers do not have glue for your nameserverscdns1.controlpanel.si, cdns2.controlpanel.si
INFO NS records at parent servers Your NS record at parent servers are:
cdns1.controlpanel.si
cdns2.controlpanel.si

These were obtained from h.gtld-servers.net. However these were obtained from authority section and not answer section. It is better if they were obtained from answer section.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
DNS Group DNS Status DNS Test Name DNS Record Information
NS
INFO NS records at your nameservers Your NS records at your nameservers are:
cdns1.controlpanel.si[TTL=300]
cdns2.controlpanel.si[TTL=300]
PASS Mismatched NS records OK. NS records at all your nameservers are identical.
PASS All nameservers respond All your nameservers responding.
PASS Recursive queries None of your nameservers allow recursive queries
PASS Zone Transfer Zone transfer not allowed by any of your nameservers
PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
PASS Missing (stealth) nameservers You have no stealth servers.
PASS Missing nameservers 2 All nameservers listed at parent servers are listed as NS records at your nameservers
PASS Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This DNS record tests only nameservers that are common at the parent and at your nameservers.
PASS No CNAMEs for domain OK. There are no CNAMEs for Do-lan.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS TCP Allowed All your nameservers allow TCP connection
PASS Stealth NS record leakage Your DNS servers doesn't leak NS record in non-NS request.
PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
FAIL Glue for NS record Your nameservers for your NS records didn't return the A records for the NS records.
DNS Group DNS Status DNS Test Name DNS Record Information
SOA
INFO SOA record Your SOA record [TTL=300] is:
Primary Name server: cdns1.controlpanel.si
Hostmaster E-mail address: server.controlpanel.si
Serial #:2023110401
Refresh: 86400
Retry: 7200
Expire: 3600000
Default: 3600
PASS SOA MNAME entry SOA MNAME cdns1.controlpanel.si is listed as a primary nameserver at your parent nameserver
PASS SOA RNAME entry OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: [email protected] (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS NS agreement on SOA Serial # OK. All your nameservers agree that your SOA serial number is 2009050102. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS report only checks the NS records listed at the parent servers (not any stealth servers).
PASS SOA Serial Your SOA serial number is: 2023110401. This appears to be in the recommended format of YYYYMMDDnn.
WARN SOA REFRESH Your SOA REFRESH interval is: 86400 which is higher than recommended. RFC 1912 recommends 1200 to 43200 seconds, low (1200) if the data is volatile or 43200 (12 hours) if it's not. If you are using NOTIFY you can set for much higher values, for instance, 1 or more days (> 86400 seconds).
WARN SOA RETRY OK. Your SOA RETRY interval is: 7200. Typical values would be 180 (3 minutes) to 900 (15 minutes) or higher.
WARN SOA EXPIRE OK. Your SOA EXPIRE interval is: 3600000 .RFC 1912 recommends 1209600 to 2419200 seconds (2-4 weeks) to allow for major outages of the zone master.
PASS SOA MINIMUM TTL OK. Your SOA MINIMUM TTL is: 3600. That is OK
DNS Group DNS Status DNS Test Name DNS Record Information
MX
FAIL MX Glue MX record look up did not send glue record for atleast 1 MX server:
alt2.aspmx.l.google.com, aspmx5.googlemail.com, aspmx4.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX name validity Good. We did not detect any invalid chars in hostnames for your MX records.
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
PASS Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers
FAIL MX Glues match MX Glue returned by nameserver for MX record doesn't match with A record of MX hostname
alt2.aspmx.l.google.com > 108.177.12.27;///// X
aspmx5.googlemail.com > 64.233.186.26;///// X
aspmx4.googlemail.com > 172.253.62.27;///// X
aspmx3.googlemail.com > 108.177.12.27;///// X
aspmx.l.google.com > 74.125.138.27;///// X
alt1.aspmx.l.google.com > 172.217.197.27;///// X
aspmx2.googlemail.com > 172.217.197.26;///// X
FAIL Duplicate MX records You have duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
INFO MX Record Your 7 records:
20    alt2.aspmx.l.google.com    [IP Address=108.177.12.27]  [TTL=300]
30    aspmx5.googlemail.com    [IP Address=64.233.186.26]  [TTL=300]
30    aspmx4.googlemail.com    [IP Address=172.253.62.27]  [TTL=300]
30    aspmx3.googlemail.com    [IP Address=108.177.12.27]  [TTL=300]
10    aspmx.l.google.com    [IP Address=74.125.138.27]  [TTL=300]
20    alt1.aspmx.l.google.com    [IP Address=172.217.197.27]  [TTL=300]
30    aspmx2.googlemail.com    [IP Address=172.217.197.26]  [TTL=300]
PASS Multiple MX records OK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you.
PASS Reverse MX A records (PTR) The reverse (PTR) record for your MX records:
108.177.12.27 -> ua-in-f27.1e100.net
64.233.186.26 -> cb-in-f26.1e100.net
172.253.62.27 -> bc-in-f27.1e100.net
108.177.12.27 -> ua-in-f27.1e100.net
74.125.138.27 -> yi-in-f27.1e100.net
172.217.197.27 -> qa-in-f27.1e100.net
172.217.197.26 -> qa-in-f26.1e100.net
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
DNS Group DNS Status DNS Test Name DNS Record Information
MAIL
PASS SPF record v=spf1 +a +mx include:_spf.google.com include:_spf.controlpanel.si ~all
this domain sends email from following domains/subdomains:_spf.google.com, _spf.controlpanel.si
WARN Sender ID record(spfv2.0) SenderID framework not implemented
WARN Domain Key Test Domain keys not implemenetd for _domainkey.Do-lan.com. Separate domainkey records may exist for subdomains and selectors under this domain. this cannot be tested.
WARN DMARC DMARC policy not found. Not enabled.
DNS Group DNS Status DNS Test Name DNS Record Information
WWW
INFO WWW A record Your WWW A record is:
www.Do-lan.com > Do-lan.com > 212.44.102.249
Your WWW is CNAME record and your CNAME entry returns A record which is good.
PASS IPs are public OK. All of your WWW IP addresses appear to be public IP addresses.
PASS HTTP Service OK: We can connect to http service on port 80.
FAIL Server http service on port 80 didn't return server information.
PASS Server Header http response header returns information about server as:
Apache
INFO Connection http connection header didn't return any information about HTTP connection
WARN Secure Header HSTS The server did not implement the HSTS (HTTP Strict Transport Security) policy. The header over the HTTPS connection was not found.
WARN Secure Header X-Frame-Options XFO clickjacking protection response header was not found. XFO enables content to be found or not within iframes via the browser.
WARN Secure Header X-Content-Type-Options The X-Content-Type-Options secure header is not set
WARN Secure Header Content-Security-Policy CSP is not defined in the policy. The return secure header does not send any feedback that the CSP has been set
WARN Secure Header X-Permitted-Cross-Domain-Policies X-Permitted-Cross-Domain-Policies was not found in the response header
WARN Secure Header Referrer-Policy The Referrer-Policy HTTP header is not set, as it is not in the Referrer header.
INFO Secure Header Clear-Site-Data Clear-Site-Data was not found in the response header
INFO Secure Header Cross-Origin-Embedder-Policy COEP response header was not found in the HTTP request
INFO Secure Header Cross-Origin-Opener-Policy COOP response header was not found in the HTTP request
WARN Secure Header Cross-Origin-Resource-Policy CORP policy not found in response header
PASS Secure Header Cache-Control Cache-Control policy header is found in HTTP responses as: Post-check=0, pre-check=0
Cache-Control belongs to the security header group that contains instructions for cashing
WARN Secure Header Permissions-Policy Permissions-Policy header was not found in the HTTP responses.
INFO Secure Header Feature-Policy Feature-Policy header was not found in the HTTP responses.
INFO Secure Header X-XSS-Protection (Deprecated) X-XSS-Protection header was not found in the HTTP responses.
INFO Secure Header HTTP Public Key Pinning (Deprecated) HPKP header was not found in the HTTP responses.
INFO Secure Header Expect-CT (Deprecated) Expect-CT header was not found in the HTTP responses.
PASS SSL / HTTPS Protocol Domain use encrypted SSL / HTTPS connection on port 443.
Check Do-lan.com SSL Certificate.
FAIL IPv6 Your domain has no IPv6 support

Click below to Copy url to clipboard for easy sharing of results: