Domain Information for 911nuebus.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 911nuebus.com

Whois

This is a cached entry from 2014-04-09 09:54:11, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.register.com

List of subdomains under 911nuebus.com

DNS report for zone 911nuebus.com

Hostmaster for zone 911nuebus.com is: root@hostmar.com
This is a cached entry from 2013-02-01 08:46:21, press here to do a realtime lookup!

  • Category Status Test Name Information
  • NS
    • info
    • NS records from
      your nameservers
    • NS records got from your nameservers are:


      ns4.hostmar.com [200.58.112.101]
      ns3.hostmar.com [200.58.112.193]

    • 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
    • Good. All nameservers listed at the parent server responded.

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

    • 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
    • ERR. All your nameservers are in the 200.58.112.0/24 subnet. (C-class)

    • 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: ns3.hostmar.com
      Hostmaster E-mail address: root@hostmar.com
      Serial #: 2012062600
      Refresh: 28800
      Retry: 7200
      Expire:2000000
      Default TTL: 14400

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

    • check
    • SOA MNAME entry
    • OK. ns3.hostmar.com That server is listed at the parent servers.

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

    • check
    • SOA REFRESH
    • OK. Your SOA REFRESH interval is: 28800. That is OK

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

    • check
    • SOA EXPIRE
    • OK. Your SOA EXPIRE value is: 2000000. Looks ok.

    • check
    • 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
    • info
    • MX Records
    • Your MX records that were reported by your nameservers are:


      0 911nuebus.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.

  • WWW
    • info
    • IPs are public
    • OK. All of your WWW IPs appear to be public IPs.

    • check
    • WWW CNAME
    • OK. No CNAME


bottom curve