Domain Information for amrekasex.com
-
IP-address(es)
174.137.132.28
(shared with 0 domains)
-
Nameserver(s)
is1.domainingdepot.com is2.domainingdepot.com -
Mailserver(s)
mx4.amrekasex.com
Keyword rankings
Search Engine Rankings
-
Google(.COM):
-
Yahoo:
Analytics / Ad-codes
- We couldn't find any analytics or ad codes on the web page
Comments
Social activity for amrekasex.com
Facebook Statistics
Social Media
Whois record for amrekasex.com
Whois
Asking
List of subdomains under amrekasex.com
- amrekasex.com A 174.137.132.28
- amrekasex.com MX 1 mx4.amrekasex.com
- amrekasex.com NS is1.domainingdepot.com
- amrekasex.com NS is2.domainingdepot.com
- amrekasex.com SOA amrekasex.com
-
NS
- NS records from
your nameservers -
NS records got from your nameservers are:
ns4.domainingdepot.com [174.137.132.38]
ns3.domainingdepot.com [174.137.132.38]
-
- Zone transfers
-
I could use the nameservers listed below to perform zone transfers. Zone transfers enables other parties to download a full list of all names under this zone. This might lead to unwanted information disclosure.
The following servers allowed zone transfers (AXFR) for amrekasex.com:
ns4.domainingdepot.com
-
- 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 174.137.132.0/24 subnet. (C-class)
-
- IPs of nameservers
are public -
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
TCP connection -
OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
-
SOA
- SOA record
-
The SOA record is:
Primary nameserver: amrekasex.com
Hostmaster E-mail address: dns@amrekasex.com
Serial #: 1
Refresh: 10800
Retry: 3600
Expire:86400
Default TTL: 7200
-
- NSs have same SOA
serial -
OK. All your nameservers agree that your SOA serial number is 1
-
- SOA MNAME entry
-
WARN. amrekasex.com 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: 1. 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: 86400. 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
- MX Records
-
Your MX records that were reported by your nameservers are:
1 mail.domainingdepot.com
-
- 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.
-
WWW
- WWW Record
-
Your www.amrekasex.com record is:
www.amrekasex.com [72.172.91.230]
-
- IPs are public
-
OK. All of your WWW IPs appear to be public IPs.
-
- WWW CNAME
-
OK. No CNAME
