Domain Information for dataline.se
- Keyword Position Monthly searches
Search Engine Rankings
- Search Sites Backlinks Indexed pages
Analytics / Ad-codes
- Service Code
- We couldn't find any analytics or ad codes on the web page
Whois record for dataline.se
WhoisThis is a cached entry from 2016-09-25 04:58:48, press here to do a realtime lookup!
# Copyright (c) 1997- IIS (The Internet Foundation In Sweden).
# All rights reserved.
# The information obtained through searches, or otherwise, is protected
# by the Swedish Copyright Act (1960:729) and international conventions.
# It is also subject to database protection according to the Swedish
# Copyright Act.
# Any use of this material to target advertising or
# similar activities is forbidden and will be prosecuted.
# If any of the information below is transferred to a third
# party, it must be done in its entirety. This server must
# not be used as a backend for a search engine.
# Result of search for registered domain names under
# the .se top level domain.
# This whois printout is printed with UTF-8 encoding.
dnssec: unsigned delegation
registrar: Loopia AB
List of subdomains under dataline.se
- DNS Record Type Target
- dataline.se A 220.127.116.11
- dataline.se MX 10 mail.davidov.se
- dataline.se MX 20 mail.davidov.com
- dataline.se NS dgate.davidov.se
- dataline.se NS ns.davidov.com
- dataline.se NS ns.davidov.se
- dataline.se SOA ns.davidov.se
- test.dataline.se A 18.104.22.168
- test.dataline.se CNAME vm3.davidov.se
- mail.dataline.se A 22.214.171.124
- www.dataline.se A 126.96.36.199
- www.dataline.se CNAME vm3.davidov.se
- Category Status Test Name Information
- Zone transfers
All of your nameservers disallows zone transfers (AXFR). This is good.
- Recursive Queries
I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
- Mismatched NS records
OK. The NS records at all your nameservers are identical.
- DNS servers responded
Good. All nameservers listed at the parent server responded.
- Multiple Nameservers
OK. You have multiple nameservers. In most cases 2 are enough, however, RFC2182 section 5 states that you must have at least 3 nameservers, and no more than 7.
- Nameservers are lame
OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
- Domain CNAMES
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other)
record is present.
- Different subnets
OK. Looks like you have nameservers on different subnets!
- IPs of nameservers
Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
- DNS servers allow
OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
- NSs have same SOA
OK. All your nameservers agree that your SOA serial number is 269
- SOA MNAME entry
WARN. vm1.davidov.se is not listed in the zone as a nameserver. This could mean that you're leaking information about a hidden master.
- SOA Serial
Your SOA serial number is: 269. Your SOA serial can pretty much be whatever you want, but most people prefer to have it in YYYYMMDD00-99 format.
- SOA REFRESH
OK. Your SOA REFRESH interval is: 14400. That is OK
- SOA RETRY
OK. Your SOA RETRY value is: 600. Looks ok.
- SOA EXPIRE
WARN. Your SOA EXPIRE interval is: 604800. We recommend that you raise it to be within the 1209600 to 2419200 range. (2 to 4 weeks)
- SOA MINIMUM
OK. Your SOA MINIMUM value is: 3600. Looks ok.
- MX Records
Your MX records that were reported by your nameservers are:
- MX is not IP
OK. All of your MX records are host names.
- Multiple MX
OK. You have multiple mailservers. (2 MX records detected)
- IPs are public
OK. All of your WWW IPs appear to be public IPs.
- WWW CNAME
OK. No CNAME