You are here: Home > DNS Reports > europa.eu

DNS Report for europa.eu

Report created on: Thu, 23 May 2013 14:08:48 GMT | permalink
Thumbnail for www.europa.eu
Parent
100
NS
97
SOA
94
MX
100
Mail
93
Web
100
A
Parent Status Message
NS Records at Parent Servers info We have successfully fetched domain's NS records from parent name server (nl.dns.eu.).
Domain NS records:
  • ns1.be.colt.net. TTL=86400 [NO GLUE4] [NO GLUE6]
  • ns1.bt.net. TTL=86400 [NO GLUE4] [NO GLUE6]
  • ns1bru.europa.eu. TTL=86400 [158.169.131.22] [NO GLUE6]
  • ns1lux.europa.eu. TTL=86400 [158.169.9.11] [NO GLUE6]
  • ns2bru.europa.eu. TTL=86400 [158.169.131.32] [NO GLUE6]
  • ns2eu.bt.net. TTL=86400 [NO GLUE4] [NO GLUE6]
  • ns2lux.europa.eu. TTL=86400 [158.169.9.30] [NO GLUE6]
Missing Glue pass OK. Parent name servers are offering glue for domain's name servers. We received name servers list and it's IP addresses from parent name server (nl.dns.eu.).
Name Servers Have A Records pass OK. Found A records for all name servers.
  • United Kingdom ns1.be.colt.net. → 212.74.77.17
  • United Kingdom ns1.bt.net. → 217.32.105.91
  • Luxembourg ns1bru.europa.eu. → 158.169.131.22
  • Luxembourg ns1lux.europa.eu. → 158.169.9.11
  • Luxembourg ns2bru.europa.eu. → 158.169.131.32
  • Netherlands ns2eu.bt.net. → 195.99.65.212
  • Luxembourg ns2lux.europa.eu. → 158.169.9.30
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.be.colt.net. → ?
  • ns1.bt.net. → ?
  • ns1bru.europa.eu. → ?
  • ns1lux.europa.eu. → ?
  • ns2bru.europa.eu. → ?
  • ns2eu.bt.net. → ?
  • ns2lux.europa.eu. → ?
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 12 NS records:
  • auth00.ns.be.uu.net. TTL=1800 [NO GLUE4] [NO GLUE6]
  • auth50.ns.be.uu.net. TTL=1800 [NO GLUE4] [NO GLUE6]
  • ns1.be.colt.net. TTL=1800 [NO GLUE4] [NO GLUE6]
  • ns1.bt.net. TTL=1800 [NO GLUE4] [NO GLUE6]
  • ns1bru.europa.eu. TTL=1800 [158.169.131.22] [NO GLUE6]
  • ns1lux.europa.eu. TTL=1800 [158.169.9.11] [NO GLUE6]
  • ns2bru.europa.eu. TTL=1800 [158.169.131.32] [NO GLUE6]
  • ns2eu.bt.net. TTL=1800 [NO GLUE4] [NO GLUE6]
  • ns2lux.europa.eu. TTL=1800 [158.169.9.30] [NO GLUE6]
  • tcbru22.cec.eu.int. TTL=1800 [158.169.131.22] [NO GLUE6]
  • tcbru25.cec.eu.int. TTL=1800 [158.169.131.32] [NO GLUE6]
  • tclux17.cec.eu.int. TTL=1800 [158.169.9.30] [NO GLUE6]
All Name Servers Responded pass OK. All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.
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 pass OK. Domain name servers are not allowing recursive queries. 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 12 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 pass OK. No lame name servers found. All of your name servers are configured to be either master or slave for your domain.
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.
  • Belgium auth00.ns.be.uu.net. → 194.7.1.19
  • Belgium auth50.ns.be.uu.net. → 194.7.15.66
  • United Kingdom ns1.be.colt.net. → 212.74.77.17
  • United Kingdom ns1.bt.net. → 217.32.105.91
  • Luxembourg ns1bru.europa.eu. → 158.169.131.22
  • Luxembourg ns1lux.europa.eu. → 158.169.9.11
  • Luxembourg ns2bru.europa.eu. → 158.169.131.32
  • Netherlands ns2eu.bt.net. → 195.99.65.212
  • Luxembourg ns2lux.europa.eu. → 158.169.9.30
  • Luxembourg tcbru22.cec.eu.int. → 158.169.131.22
  • Luxembourg tcbru25.cec.eu.int. → 158.169.131.32
  • Luxembourg tclux17.cec.eu.int. → 158.169.9.30
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.
  • auth00.ns.be.uu.net. → 2001:600:1c0:e000::35:4
  • auth50.ns.be.uu.net. → 2001:600:1c0:e001::35:4
  • ns1.be.colt.net. → ?
  • ns1.bt.net. → ?
  • ns1bru.europa.eu. → ?
  • ns1lux.europa.eu. → ?
  • ns2bru.europa.eu. → ?
  • ns2eu.bt.net. → ?
  • ns2lux.europa.eu. → ?
  • tcbru22.cec.eu.int. → ?
  • tcbru25.cec.eu.int. → ?
  • tclux17.cec.eu.int. → ?
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 warn WARNING: Found stealth name servers:
  • auth00.ns.be.uu.net.
  • auth50.ns.be.uu.net.
  • tcbru22.cec.eu.int.
  • tcbru25.cec.eu.int.
  • tclux17.cec.eu.int.
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 pass OK. All name servers are allowing TCP connections. 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 on Separate Networks pass OK. Name servers are dispersed on 7 different C class networks:
  • 158.169.131.0/24:
    • ns1bru.europa.eu.
    • ns2bru.europa.eu.
    • tcbru22.cec.eu.int.
    • tcbru25.cec.eu.int.
  • 158.169.9.0/24:
    • ns1lux.europa.eu.
    • ns2lux.europa.eu.
    • tclux17.cec.eu.int.
  • 194.7.1.0/24:
    • auth00.ns.be.uu.net.
  • 194.7.15.0/24:
    • auth50.ns.be.uu.net.
  • 195.99.65.0/24:
    • ns2eu.bt.net.
  • 212.74.77.0/24:
    • ns1.be.colt.net.
  • 217.32.105.0/24:
    • ns1.bt.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:
  • 158.169.131.22: "not allowed"
  • 158.169.131.32: "not allowed"
  • 158.169.9.11: "not allowed."
  • 158.169.9.30: "not allowed"
  • 194.7.1.19: "unknown"
  • 194.7.15.66: "unknown"
  • 195.99.65.212: "This information is prohibited."
  • 2001:600:1c0:e000::35:4: "unknown"
  • 2001:600:1c0:e001::35:4: "unknown"
  • 212.74.77.17: "Colt"
  • 217.32.105.91: "This information is restricted, Your query has been logged."
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.
SOA Status Message
Check SOA Record info Domain SOA Record:
  • Primary nameserver: ns1lux.europa.eu.
  • Hostmaster (e-mail): snet.ec.europa.eu.
  • Serial: 2013052201
  • Refresh: 3600
  • Retry: 600
  • Expire: 604800
  • Minimum TTL: 1800
Name Servers Agreement on Serial Number pass OK. All name servers (7) have the same serial number [2013052201]. 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 [2013052201]. 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 ns1lux.europa.eu. 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 snet@ec.europa.eu. (snet.ec.europa.eu.). 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 3600. 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 600. 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 604800. 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 warn WARNING: Minimum TTL value is 1800. Recommended values [3600 .. 86400] (1 hour ... 1 day). 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.
MX Status Message
MX Records info Your name servers returned 6 MX records:
  • 10 s-dc-edg003-z.mail.ec.europa.eu. TTL=1800
  • 10 s-dc-edg006-q.mail.ec.europa.eu. TTL=1800
  • 10 s-dc-edg007-q.mail.ec.europa.eu. TTL=1800
  • 10 s-dc-edg008-q.mail.ec.europa.eu. TTL=1800
  • 10 s-dc-edg001-z.mail.ec.europa.eu. TTL=1800
  • 10 s-dc-edg002-z.mail.ec.europa.eu. TTL=1800
Identical MX Records pass OK. All name servers returned identical MX records.
Mail Servers Have A Records pass OK. Found A records for all mail servers.
  • Luxembourg s-dc-edg001-z.mail.ec.europa.eu. → 147.67.11.2
  • Luxembourg s-dc-edg002-z.mail.ec.europa.eu. → 147.67.11.3
  • Luxembourg s-dc-edg003-z.mail.ec.europa.eu. → 147.67.11.4
  • Luxembourg s-dc-edg006-q.mail.ec.europa.eu. → 147.67.249.2
  • Luxembourg s-dc-edg007-q.mail.ec.europa.eu. → 147.67.249.3
  • Luxembourg s-dc-edg008-q.mail.ec.europa.eu. → 147.67.249.6
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records notice NOTICE: While reading domain NS records at parent mail servers, we found mail servers without AAAA records.
  • s-dc-edg001-z.mail.ec.europa.eu. → ?
  • s-dc-edg002-z.mail.ec.europa.eu. → ?
  • s-dc-edg003-z.mail.ec.europa.eu. → ?
  • s-dc-edg006-q.mail.ec.europa.eu. → ?
  • s-dc-edg007-q.mail.ec.europa.eu. → ?
  • s-dc-edg008-q.mail.ec.europa.eu. → ?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records pass OK. All mail servers have reverse DNS entries configured correctly.
Server IP PTR (Reverse) IPs
s-dc-edg003-z.mail.ec.europa.eu. 147.67.11.4 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4
s-dc-edg006-q.mail.ec.europa.eu. 147.67.249.2 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4
s-dc-edg007-q.mail.ec.europa.eu. 147.67.249.3 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4
s-dc-edg008-q.mail.ec.europa.eu. 147.67.249.6 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4
s-dc-edg001-z.mail.ec.europa.eu. 147.67.11.2 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4
s-dc-edg002-z.mail.ec.europa.eu. 147.67.11.3 out.mail.ec.europa.eu. 147.67.11.6, 147.67.249.6, 147.67.11.3, 147.67.11.5, 147.67.249.3, 147.67.11.2, 147.67.249.5, 147.67.249.2, 147.67.249.4, 147.67.11.4

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.
  • s-dc-edg001-z.mail.ec.europa.eu.: 
    220 S-DC-EDG001-Z.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:08:14 +0200
  • s-dc-edg002-z.mail.ec.europa.eu.: 
    220 S-DC-EDG002-Z.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:09:10 +0200
  • s-dc-edg003-z.mail.ec.europa.eu.: 
    220 S-DC-EDG003-Z.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:09:09 +0200
  • s-dc-edg006-q.mail.ec.europa.eu.: 
    220 S-DC-EDG006-Q.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:09:04 +0200
  • s-dc-edg007-q.mail.ec.europa.eu.: 
    220 S-DC-EDG007-Q.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:09:04 +0200
  • s-dc-edg008-q.mail.ec.europa.eu.: 
    220 S-DC-EDG008-Q.rcnet.cec.eu.int Microsoft ESMTP MAIL Service ready at Thu, 23 May 2013 16:09:02 +0200
To receive emails, mail servers should allow TCP connections on port 25.
Mail Greeting notice NOTICE: I've found differences between mail server host names and greeting host name. The following mail servers claims to be other hosts (reverse DNS checks may be wrong):
  • s-dc-edg001-z.mail.ec.europa.eu. → s-dc-edg001-z.rcnet.cec.eu.int
  • s-dc-edg002-z.mail.ec.europa.eu. → s-dc-edg002-z.rcnet.cec.eu.int
  • s-dc-edg003-z.mail.ec.europa.eu. → s-dc-edg003-z.rcnet.cec.eu.int
  • s-dc-edg006-q.mail.ec.europa.eu. → s-dc-edg006-q.rcnet.cec.eu.int
  • s-dc-edg007-q.mail.ec.europa.eu. → s-dc-edg007-q.rcnet.cec.eu.int
  • s-dc-edg008-q.mail.ec.europa.eu. → s-dc-edg008-q.rcnet.cec.eu.int
Accepts Postmaster Address pass OK. All mail servers are accepting emails to postmaster@europa.eu address:
  • s-dc-edg001-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg002-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg003-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg006-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg007-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg008-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <postmaster@europa.eu>
<< 250 2.1.5 Recipient 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@europa.eu address:
  • s-dc-edg001-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg002-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg003-z.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg006-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg007-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
  • s-dc-edg008-q.mail.ec.europa.eu. 
    >> MAIL FROM: <dnsreport@dnsinspect.com>
<< 250 2.1.0 Sender OK
>> RCPT TO: <abuse@europa.eu>
<< 250 2.1.5 Recipient OK
Check SPF record warn WARNING: Domain doesn't have SPF record. 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 skip No SPF type records found. 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 europa.eu. resolves to:
  • Luxembourg 147.67.136.2
  • Luxembourg 147.67.119.2
  • Luxembourg 147.67.119.102
Domain Name IPs are Public pass OK. No private IPs found for europa.eu.. Web servers using private IPs can't be reached from the Internet.
Resolve WWW pass OK. Domain www.europa.eu. resolves to:
  • Luxembourg 147.67.136.2
  • Luxembourg 147.67.119.2
  • Luxembourg 147.67.119.102
WWW IPs are Public pass OK. No private IPs found for www.europa.eu.. Web servers using private IPs can't be reached from the Internet.

Report completed in 13.46 seconds.

© 2008 - 2013 DNSInspect.com
Powered by Jekyll & Go