Inycom.es DNS record lookup check

DNS record types tested in our free DNS record 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 Inycom.es:

DNS Record DNS Check DNS Test Name DNS Record Information
PARENT
PASS Missing Direct Parent check OK. Your direct parent zone exists, SOA of parent zone es is ns1.nic.es 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 nameserversns.gestiondecuenta.com, ns2.gestiondecuenta.com, ns3.gestiondecuenta.com, ns4.gestiondecuenta.com
INFO NS records at parent servers Your NS record at parent servers are:
ns.gestiondecuenta.com
ns2.gestiondecuenta.com
ns3.gestiondecuenta.com
ns4.gestiondecuenta.com

These were obtained from a.nic.es. 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
FAIL Parent nameservers have your nameservers listed Your nameservers not listed in parent servers: ns4.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns.dinahosting.com
DNS Group DNS Status DNS Test Name DNS Record Information
NS
INFO NS records at your nameservers Your NS records at your nameservers are:
ns2.dinahosting.com[TTL=300]
ns3.dinahosting.com[TTL=300]
ns4.dinahosting.com[TTL=300]
ns.dinahosting.com[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 4 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.
FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The report will not query these servers, so you need to be very careful that they are working properly.
ns2.dinahosting.com
ns3.dinahosting.com
ns4.dinahosting.com
ns.dinahosting.com
FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns.gestiondecuenta.com, ns2.gestiondecuenta.com, ns3.gestiondecuenta.com, ns4.gestiondecuenta.com
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 Inycom.es. 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: ns.dinahosting.com
Hostmaster E-mail address: dnsadmin.dinahosting.com
Serial #:2019110501
Refresh: 3600
Retry: 120
Expire: 1209600
Default: 300
FAIL SOA MNAME entry SOA MNAME ns.dinahosting.com is not 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: 2019110501. This appears to be in the recommended format of YYYYMMDDnn.
INFO SOA REFRESH OK. Your SOA REFRESH interval is: 3600. 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: 120. Typical values would be 180 (3 minutes) to 900 (15 minutes) or higher.
INFO SOA EXPIRE OK. Your SOA EXPIRE interval is: 1209600 .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: 300. 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:
inycom-es.mail.protection.outlook.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
inycom-es.mail.protection.outlook.com > 52.101.73.22;///// X
PASS Duplicate MX records OK. You do not have any 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 1 records:
10    inycom-es.mail.protection.outlook.com    [IP Address=52.101.73.22]  [TTL=300]
FAIL Multiple MX records You need to have multiple MX records so 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:
52.101.73.22 -> mail-am7pr05cu00106.inbound.protection.outlook.com
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 include:spf.hornetsecurity.com include:spf.protection.outlook.com ip4:212.75.174.233 include:servers.mcsv.net include:spf.emailsignatures365.com include:marketing.dynamics.com include:email.signaturit.com include:spf.a3asesor-rrhh.com ~all
d365mktkey=4skp92608gtymciywwe6hthk8
2A701wYATB4XJbsDZXXgbTQPIwdg1FwVt4Ra0EOrFlULGOnQ0euldzaleFcEBXAV/NwGcmSpV8yENiQ8b3jgOQ==
atlassian-domain-verification=oMJj5luh0mAqdbxezSj8FIGsaamOXktr7r/cgvuGoi/BWUMZDmpwqDCMR9zNXpxf
twilio-domain-verification=bb40c62daedd66e0d7b617e0a993aad3
apple-domain-verification=i9GO4Nth9GpK53I6
google-site-verification=YZNlwdj0EeLSjgmnmCoaV9VpdO9W5PP42Aa4cLeqKTg
this domain sends email from following domains/subdomains:spf.hornetsecurity.com, spf.protection.outlook.com, servers.mcsv.net, spf.emailsignatures365.com, marketing.dynamics.com, email.signaturit.com, spf.a3asesor-rrhh.com
this domain sends email from following IP/Range: 212.75.174.233
WARN Sender ID record(spfv2.0) SenderID framework not implemented
PASS Domain Key Test t=y; o=~;
The interim sending domain policy
this domain may sign some email with DomainKeys available under selectors This implementation is in test mode.
  • The public key certificate is not tested
  • 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.Inycom.es > inycomweb-lb-1922170791.eu-west-1.elb.amazonaws.com > 34.253.127.100
    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.
    INFO Server Header http response header didn't return any server information
    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
    WARN Secure Header Cache-Control Cache-Control policy header not found in HTTP responses
    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 SSL Certificate.
    FAIL IPv6 Your domain has no IPv6 support

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