Nvenergy.com 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 Nvenergy.com:

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 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 nameservers
INFO NS records at parent servers Your NS record at parent servers are:
ns-116.awsdns-14.com[IP Address=205.251.192.116][TTL=172800]

These were obtained from b.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:
ns-116.awsdns-14.com[TTL=172800]
ns-1164.awsdns-17.org[TTL=172800]
ns-2042.awsdns-63.co.uk[TTL=172800]
ns-807.awsdns-36.net[TTL=172800]
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.
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 No CNAMEs for domain OK. There are no CNAMEs for Nvenergy.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=900] is:
Primary Name server: ns-116.awsdns-14.com
Hostmaster E-mail address: awsdns-hostmaster.amazon.com
Serial #:1
Refresh: 7200
Retry: 900
Expire: 1209600
Default: 86400
PASS SOA MNAME entry SOA MNAME ns-116.awsdns-14.com 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).
FAIL SOA Serial Your SOA serial number is: 1. This doesn't appears to be in the recommended format of YYYYMMDDnn.
INFO SOA REFRESH OK. Your SOA REFRESH interval is: 7200. 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: 900. 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: 86400. 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:
nvenergy-com.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
nvenergy-com.mail.protection.outlook.com > 52.101.194.0;///// 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    nvenergy-com.mail.protection.outlook.com    [IP Address=52.101.194.0]  [TTL=900]
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.194.0 -> mail-ch5pr02cu00200.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 MS=EDAA8F6108BE4C2CA6A7C6C53051CF4388EC9797
MS=ms50921559
OATI:B4Rvr7a378U55tEt724V7a@xMjYLD878y7@
adobe-sign-verification=9c2e09d755b5cdb924fe278c11ac392a
apple-domain-verification=Vnn2npuM5FjPulsm
atlassian-domain-verification=Q4NMbtQQ6dhEcaF+j360i6l0pfkotMPYEdP2bVlr21Oxoa2O6tvZVvSKb/jVnk2w
atlassian-domain-verification=ZRiL4RN4HzBdMvH5GDx+laTgjBo5p6+e3FIjZJXUW4EWRJ3jMCvf3SGxzwnj+VPe
facebook-domain-verification=8ze15sp25ufmyfp34snr8glvspu998
google-site-verification=RQXXP4BXSK8oUmWeCuRBsf50GM_1fasjeBB6ly9mJu8
google-site-verification=d6PYidxP3A84kNfuNALb6DinBQ3HFWwICEvL60AJWfE
ibmid=cfabedce-f243-4d97-8e4e-262ab6fdf489
knowbe4-site-verification=2829896b8a765c4c200bf27f9db03f6a
mandrill_verify.dz1p2odxJEtZTItyqSyO7w
ooqhpzQ1w7KlVVDHZEMYOXeo3dnfyT5A/Wqlet/HLrlx6g9D/3S8bnVqWGY/lujuVSmqmDv8SPWbPvsT2O/U5Q==
v=spf1 ip4:131.219.200.5 ip4:131.219.200.9 ip4:131.219.5.76/30 ip4:131.219.200.15 ip4:131.219.200.16 ip4:131.219.1.30 ip4:131.219.1.31 ip4:192.206.180.200 ip4:129.145.79.112 ip4:129.145.79.113 include:spf.protection.outlook.com -all
this domain sends email from following domains/subdomains:spf.protection.outlook.com
this domain sends email from following IP/Range: 131.219.200.5, 131.219.200.9, 131.219.5.76/30, 131.219.200.15, 131.219.200.16, 131.219.1.30, 131.219.1.31, 192.206.180.200, 129.145.79.112, 129.145.79.113
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
  • The public key certificate is not tested
  • Separate domainkey records may exist for subdomains and selectors under this domain. this cannot be tested.
  • PASS DMARC v=DMARC1; p=reject; pct=100; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=0; adkim=r; aspf=r; rf=afrf; ri=86400;
    DNS Group DNS Status DNS Test Name DNS Record Information
    WWW
    INFO WWW A record Your WWW A record is:
    www.Nvenergy.com > 192.206.180.63
    You have separate A record for www
    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.
    INFO Server http service on port 80 returns server information as
    BigIP
    PASS Server Header http response header returns information about server as:
    BigIP
    PASS Connection http connection header return connection as: Close
    PASS Secure Header HSTS The server implemented the HSTS (HTTP Strict Transport Security) policy by adding a header over the HTTPS connection as: Max-age=31536000; includeSubDomains
    PASS Secure Header X-Frame-Options XFO response header that protects against clickjacking is found as: Deny
    XFO enables content to be found or not within iframes via the browser.
    PASS Secure Header X-Content-Type-Options The secure X-Content-Type-Options header is set as: Nosniff
    The browser must interpret the file exactly as it is specified in the Content-Type HTTP header
    PASS Secure Header Content-Security-Policy The return secure header sends feedback that the CSP has been found and specified. CSP is defined in the policy as: Frame-ancestors *.nvenergy.com *.bidgely.com *.ecofactor.com *.ecobee.com *.cleanpowerdemo.com file://*
    CSP prevents various types of attacks, such as cross-site scripting and other types of cross-site injection
    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: Max-age=3600
    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 SSL Certificate.
    FAIL IPv6 Your domain has no IPv6 support

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