Aiguesdebarcelona.cat ⇒ DNS Record Check

DNS & IP Record Check for Aiguesdebarcelona.cat

This tool gives you a detailed look at Aiguesdebarcelona.cat DNS setup. It checks various parts of the DNS records to ensure everything is functioning smoothly and securely.

DNS Record Group Breakdown:

Our DNS & IP record check is organized into 6 main groups, each focusing on different aspects of your domain's DNS configuration. Each group tests key components to ensure optimal domain performance:

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

Test Status Summary:

To help you better understand the results, our team has categorized the outcomes into four statuses:

PASS - No issues found in the DNS record.
FAIL - We detected a DNS record error that needs your attention.
WARN - A minor DNS record issue was found.
INFO - Informational data about the DNS record with no errors detected.

To ensure the integrity and security of Aiguesdebarcelona.cat DNS data, use our DNSSEC check tool. This test provides a deeper analysis, focusing on digital signatures, security, and integrity of the DNS records.

Below is an overview of the results from our comprehensive DNS lookup for the domain Aiguesdebarcelona.cat:

DNS Group

DNS Check

DNS Record Type

DNS Data Information

PARENT

PASS

Missing Direct Parent check

OK. Your direct parent zone exists, SOA of parent zone cat is anyc1.irondns.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 nameserversns2-03.azure-dns.net, ns4-03.azure-dns.info, ns1-03.azure-dns.com, ns3-03.azure-dns.org

INFO

NS records at parent servers

Your NS record at parent servers are:
ns2-03.azure-dns.net
ns4-03.azure-dns.info
ns1-03.azure-dns.com
ns3-03.azure-dns.org

These were obtained from nsc.nic.de. 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 Record Type

DNS Data Information

INFO

NS records at your nameservers

Your NS records at your nameservers are:

ns1-03.azure-dns.com		[TTL=172800]
ns2-03.azure-dns.net		[TTL=172800]
ns3-03.azure-dns.org		[TTL=172800]
ns4-03.azure-dns.info		[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

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 Aiguesdebarcelona.cat. 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 Record Type	DNS Data Information
SOA
	INFO	SOA record	Your SOA record [TTL=3600] is: Primary Name server: ns1-03.azure-dns.com Hostmaster E-mail address: azuredns-hostmaster.microsoft.com Serial #:1 Refresh: 3600 Retry: 300 Expire: 2419200 Default: 300
	PASS	SOA MNAME entry	SOA MNAME ns1-03.azure-dns.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: 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: 300. Typical values would be 180 (3 minutes) to 900 (15 minutes) or higher.
	INFO	SOA EXPIRE	OK. Your SOA EXPIRE interval is: 2419200 .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 Record Type	DNS Data Information
MX
	FAIL	MX Glue	MX record look up did not send glue record for atleast 1 MX server: aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.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 aspmx.l.google.com > 74.125.136.27;///// X alt4.aspmx.l.google.com > 64.233.186.27;///// X alt3.aspmx.l.google.com > 172.253.62.27;///// X alt2.aspmx.l.google.com > 108.177.12.27;///// X alt1.aspmx.l.google.com > 172.217.197.26;///// 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 5 records: 1 aspmx.l.google.com [IP Address=74.125.136.27] [TTL=3600] 10 alt4.aspmx.l.google.com [IP Address=64.233.186.27] [TTL=3600] 10 alt3.aspmx.l.google.com [IP Address=172.253.62.27] [TTL=3600] 5 alt2.aspmx.l.google.com [IP Address=108.177.12.27] [TTL=3600] 5 alt1.aspmx.l.google.com [IP Address=172.217.197.26] [TTL=3600]
	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: 74.125.136.27 -> yr-in-f27.1e100.net 64.233.186.27 -> cb-in-f27.1e100.net 172.253.62.27 -> bc-in-f27.1e100.net 108.177.12.27 -> ua-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 Record Type	DNS Data Information
MAIL
	PASS	SPF record	v=spf1 include:spf.mailjet.com include:spf2.agbar.es mx include:spf.protection.outlook.com include:servers.mcsv.net ip4:95.130.52.129 include:_spf.google.com -all
	PASS	TXT record	google-site-verification=ulsTA0mPKLhSgcWwVtAuK-m9MyvCj8G6L2ekcQJJJKg
	PASS	TXT record	google-site-verification=O_NuzOhJYdhuVWy9Z5cgpK6jX4LbKVqlJpvVOLfYlWo
	PASS	TXT record	pfqr1264sg1qhfc3lttejrgj5r
	PASS	TXT record	atlassian-domain-verification=hmYPGaII8sKrRBNSasSAC6s18p87K8SGkEKwMoNWHilsk7vca5iAabqkbluFVFmJ
	PASS	TXT record	MS=ms31781867
	PASS	TXT record	autodesk-domain-verification=u_jL4BWVCYB2gmB4CUFz
	PASS	TXT record	f5mlnk484p89g969km56g2ppd9
	PASS	TXT record	autodesk-domain-verification=BKCcZQ7OPtO-jWWqI8IS
	PASS	TXT record	atlassian-domain-verification=REJsEXcGzDSSLeqsLVBerJzaWdtODhvF3XvV4NjhTeq71VzJlbCiF7T7BqzC6Klp
PASS	TXT record	google-gws-recovery-domain-verification=40060039
PASS	TXT record	globalsign-domain-verification=E41E92C8AF47D50AAFAE806844A8E85B
PASS	TXT record	google-site-verification=awKoedwBITvfFl6XuSwzvpzPShgAqVoMfXOpwHb2lRQ
PASS	TXT record	hes=ce15ca61a1661f1cef55dc764a2a5458
WARN	Sender ID record(spfv2.0)	SenderID framework not implemented
WARN	Domain Key Test	Domain keys not implemenetd for _domainkey.Aiguesdebarcelona.cat. Separate domainkey records may exist for subdomains and selectors under this domain. this cannot be tested.
PASS	DMARC	v=DMARC1; p=quarantine; rua=mailto:[email protected];

DNS Group	DNS Status	DNS Record Type	DNS Data Information
WWW
	INFO	WWW A record	Your WWW A record is: www.Aiguesdebarcelona.cat > 7xh79.x.incapdns.net. Resolved IP: 45.60.12.134 Your WWW is CNAME record and your CNAME entry returns A record which is good. WA & DA Score for 7xh79.x.incapdns.net
	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. View SSL Certificate: Aiguesdebarcelona.cat.
	FAIL	IPv6	Your domain has no IPv6 support

Click below to copy URL to clipboard for easy sharing of results: