Domain Information for fagert.se
- Category Information
(shared with 0 domains)
ns1.loopia.se184.108.40.206 (280232) ns2.loopia.se220.127.116.11 (280226)
ALT1.ASPMX.L.GOOGLE.COM18.104.22.168 (3297733) ALT2.ASPMX.L.GOOGLE.COM ASPMX.L.GOOGLE.COM22.214.171.124 (116433) ASPMX2.GOOGLEMAIL.COM126.96.36.199 (6) ASPMX3.GOOGLEMAIL.COM188.8.131.52 (3058824)
- 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 fagert.se
WhoisThis is a cached entry from 2015-12-10 22:13:53, 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: signed delegation
registrar: Loopia AB
List of subdomains under fagert.se
- DNS Record Type Target
- fagert.se A 184.108.40.206
- fagert.se MX 1 ASPMX.L.GOOGLE.COM
- fagert.se MX 5 ALT1.ASPMX.L.GOOGLE.COM
- fagert.se MX 5 ALT2.ASPMX.L.GOOGLE.COM
- fagert.se MX 10 ASPMX2.GOOGLEMAIL.COM
- fagert.se MX 10 ASPMX3.GOOGLEMAIL.COM
- fagert.se NS ns1.loopia.se
- fagert.se NS ns2.loopia.se
- fagert.se SOA ns1.loopia.se
- fagert.se TXT v=spf1 include:_spf.google.com ip4:220.127.116.11 ip4:18.104.22.168 ~all
- www.fagert.se A 22.214.171.124
- *.fagert.se A 126.96.36.199
- Category Status Test Name Information
- Zone transfers
All of your nameservers disallows zone transfers (AXFR). This is good.
- Recursive Queries
All of your nameservers disallows recursive queries. This is good.
- 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
ERR. All your nameservers are in the 188.8.131.52/24 subnet. (C-class)
- 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 1296794110
- SOA MNAME entry
OK. ns1.loopia.se That server is listed at the parent servers.
- SOA Serial
Your SOA serial number is: 1296794110. 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: 10800. 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
WARN. Your SOA MINIMUM interval is: 86400. We recommend that you lower it to be within the 3600 to 10800 range. (1 to 3 hours)
- 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
WARN. You have one MX-record. You should look into getting a backup mailserver for increased redundancy.
- IPs are public
OK. All of your WWW IPs appear to be public IPs.
- WWW CNAME
OK. No CNAME