Domain Information for afishermansfriend.co.uk
- 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 afishermansfriend.co.uk
WhoisThis is a cached entry from 2016-10-09 11:53:48, press here to do a realtime lookup!
28 bridgefield street
Nominet was able to match the registrant's name and address against a 3rd party data source on 05-Jul-2013
GoDaddy.com, LLP. [Tag = GODADDY]
Registered on: 05-Jul-2013
Expiry date: 05-Jul-2017
Last updated: 18-Jul-2016
Registered until expiry date.
WHOIS lookup made at 10:53:49 09-Oct-2016
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2016.
You may not access the .uk WHOIS or use any data from it except as permitted
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.
List of subdomains under afishermansfriend.co.uk
DNS report for zone afishermansfriend.co.uk
- 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
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 2013081002
- SOA MNAME entry
OK. ns67.domaincontrol.com That server is listed at the parent servers.
- SOA Serial
Your SOA serial number is: 2013081002. 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: 28800. 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: 600. We recommend that you raise 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.