DNS Reports for: bit.ly

Tuesday 17. October 2017

Category: Parent

INFO Domain NS Records
Nameserver records returned by the parent servers are:

Domain IP Address TTL
ns-1372.awsdns-43.org 205.251.197.92 86145
ns-1766.awsdns-28.co.uk 205.251.198.230 86145
ns-276.awsdns-34.com 205.251.193.20 86145
ns-705.awsdns-24.net 205.251.194.193 86145
ns1.p35.dynect.net 208.78.70.35 86145
ns2.p35.dynect.net 204.13.250.35 86145
ns3.p35.dynect.net 208.78.71.35 86145
ns4.p35.dynect.net 204.13.251.35 86145
PASS TLD Parent Check
Good. phloem.uoregon.edu, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
PASS Nameservers Are Listed
Good. The parent server phloem.uoregon.edu has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
FAIL DNS Parent Sent Glue
This is bad. The parent nameserver is not sending GLUE for your nameservers.
PASS Nameserver A Records
Good. Every nameserver listed has A records. This is a must if you want to be found..

Category: Name Servers

INFO NS Records
NS records from your nameservers listed at the parent NS are:

Domain IP Address TTL
ns-1372.awsdns-43.org 205.251.197.92 86400
ns-1766.awsdns-28.co.uk 205.251.198.230 86400
ns-276.awsdns-34.com 205.251.193.20 86400
ns-705.awsdns-24.net 205.251.194.193 86400
ns1.p35.dynect.net 208.78.70.35 86400
ns2.p35.dynect.net 204.13.250.35 86400
ns3.p35.dynect.net 208.78.71.35 86400
ns4.p35.dynect.net 204.13.251.35 86400
PASS Recursive Queries
Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
FAIL Same Glue
The glue records from your parent name servers do not match the glue recordsfrom your nameservers.
INFO Glue For NS Records
INFO: GLUE was not sent when I asked your nameservers for your NS records. This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records.
PASS Mismatched NS Records
OK. The NS records at all your nameservers are identical.
PASS DNS Servers Responded
Good. All nameservers listed at the parent server responded.
PASS Nameservers Are Valid
OK. All of the NS records that your nameservers report seem valid.
PASS Multiple Nameservers
Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is common and ok.
PASS Nameservers Are Lame
OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

Category: SOA

INFO SOA record
The SOA record is:

Primary nameserver: ns-1372.awsdns-43.org
Hostmaster: awsdns-hostmaster.amazon.com
Serial #: 1
Refresh: 7200
Retry: 900
Expire: 1209600
TTL: 86400

Category: MX

INFO MX records
MX records reported by your nameservers:

ASPMX3.GOOGLEMAIL.COM
ASPMX2.GOOGLEMAIL.COM
ASPMX.L.GOOGLE.COM
ALT1.ASPMX.L.GOOGLE.COM
ALT2.ASPMX.L.GOOGLE.COM
FAIL Different MS Records At Nameservers
Oops. Some of your nameservers have different sets of MX records.
PASS MX Name Validity
Good. I did not detect any invalid MX hostname records.
PASS MX IPs Are Public
OK. All of your MX records appear to use public IPs.
PASS MX CNAME Check
OK. No problems here.
PASS MX A Request Returns CNAME
OK. No CNAMEs returned for A records lookups.
PASS MX Is Not IP
OK. All of your MX records are host names.
PASS Number Of MX Records
Good. Looks like you have multiple MX records at all your nameservers. This is a good thing and will help in preventing loss of mail.
PASS Mismatched MX A Records
OK. I did not detect differing IPs for your MX records.
PASS Duplicate MX A Records
OK. You have some duplicate MX records (MX records with the same IPs). This is not that good but if you know what you are doing than it's ok.

Category: Web

INFO WWW A Record
A Record: www.bit.ly

Alias: bit.ly.

IP Addresses:
  • 67.199.248.11
  • 67.199.248.10
PASS IP Addresses Public
OK. All of your WWW IPs appear to be public IPs.
PASS WWW CNAME
OK. You have a WWW cname.