Domain Information for wirepathdns.com


Keyword rankings

Search Engine Rankings

  • Search Sites Backlinks Indexed pages
  • Google(.COM): loader loader
  • Yahoo: loader loader

Analytics / Ad-codes

  • Service Code
  • We couldn't find any analytics or ad codes on the web page

Comments

Whois record for wirepathdns.com

Whois

This is a cached entry from 2013-08-25 03:50:02, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.godaddy.com

List of subdomains under wirepathdns.com

DNS report for zone wirepathdns.com

Hostmaster for zone wirepathdns.com is: hostmaster@ddns.local
This is a cached entry from 2013-01-28 15:19:42, press here to do a realtime lookup!

  • Category Status Test Name Information
  • NS
    • info
    • Zone transfers
    • All of your nameservers disallows zone transfers (AXFR). This is good.

    • info
    • Recursive Queries
    • All of your nameservers disallows recursive queries. This is good.

    • check
    • Mismatched NS records
    • OK. The NS records at all your nameservers are identical.

    • check
    • DNS servers responded
    • The following of your nameservers are down:

      ns6.wirepathdns.com
      ns4.wirepathdns.com
      ns7.wirepathdns.com
      sp0331g.ddns.local
      ns3.wirepathdns.com
      ns5.wirepathdns.com
      spu12414c.ddns.local

    • check
    • Multiple Nameservers
    • ERR. You have too many nameservers. If you have more than 7 nameservers the DNS reply will become too large, and will provide little to none extra redundancy. We recommend that you remove a few.

    • check
    • Nameservers are lame
    • OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

    • check
    • 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.

    • check
    • Different subnets
    • OK. Looks like you have nameservers on different subnets!

    • check
    • 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

    • check
    • 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
    • info
    • SOA record
    • The SOA record is:
      Primary nameserver: spu12414c.ddns.local
      Hostmaster E-mail address: hostmaster@ddns.local
      Serial #: 295076
      Refresh: 900
      Retry: 600
      Expire:600
      Default TTL: 30

    • info
    • NSs have same SOA
      serial
    • OK. All your nameservers agree that your SOA serial number is 295076

    • check
    • SOA MNAME entry
    • OK. spu12414c.ddns.local That server is listed at the parent servers.

    • info
    • SOA Serial
    • Your SOA serial number is: 295076. Your SOA serial can pretty much be whatever you want, but most people prefer to have it in YYYYMMDD00-99 format.

    • check
    • SOA REFRESH
    • WARN Your SOA REFRESH interval is: 900. We recommend that you raise it to be within the 1200 to 43200 range. (20 minutes to 12 hours)

    • check
    • SOA RETRY
    • OK. Your SOA RETRY value is: 600. Looks ok.

    • check
    • SOA EXPIRE
    • WARN. Your SOA EXPIRE interval is: 600. We recommend that you raise it to be within the 1209600 to 2419200 range. (2 to 4 weeks)

    • check
    • SOA MINIMUM
    • WARN. Your SOA MINIMUM interval is: 30. We recommend that you raise it to be within the 3600 to 10800 range. (1 to 3 hours)

  • MX
    • info
    • MX Records
    • Your MX records that were reported by your nameservers are:


      10 wirepathdns.com

    • check
    • MX is not IP
    • OK. All of your MX records are host names.

    • check
    • Multiple MX
    • WARN. You have one MX-record. You should look into getting a backup mailserver for increased redundancy.


bottom curve