Report for bjs.com
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
m.gtld-servers.net.).
Domain NS records:
-
a1-71.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
-
a12-65.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
-
a13-67.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
-
a14-67.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
-
a16-67.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
-
a7-64.akam.net. TTL=172800
[NO GLUE4]
[NO GLUE6]
Test ignored, name servers are located outside of current zone.
Name Servers Have A Records
OK.
Found A records for all name servers.
- a1-71.akam.net. → 193.108.91.71
- a12-65.akam.net. → 184.26.160.65
- a13-67.akam.net. → 2.22.230.67
- a14-67.akam.net. → 184.26.161.67
- a16-67.akam.net. → 23.211.132.67
- a7-64.akam.net. → 23.61.199.64
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
OK.
Found AAAA records for all name servers.
- a1-71.akam.net. → 2600:1401:2::47
- a12-65.akam.net. → 2600:1480:f000::41
- a13-67.akam.net. → 2600:1480:800::43
- a14-67.akam.net. → 2600:1480:1800::43
- a16-67.akam.net. → 2600:1406:1b::43
- a7-64.akam.net. → 2600:1406:32::40
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Your name servers returned
6 NS records:
-
a1-71.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
-
a12-65.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
-
a13-67.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
-
a14-67.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
-
a16-67.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
-
a7-64.akam.net. TTL=600
[NO GLUE4]
[NO GLUE6]
All Name Servers Responded
OK.
All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.
OK.
No differences found.
The glue provided by the parent name servers has to match
the data provided by the authoritative name servers.
OK.
Domain name servers are not allowing recursive queries.
On all name servers which acts as caching name servers recursive queries should be restricted to local networks.
Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks.
Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic,
email and other traffic to malicious hosts compromising security.
OK.
Domain has 6 name servers. Recommended number,
between 2 and 7 name servers (RFC 2182 recommends to have at
least 3 authoritative name servers for domains).
OK.
All your name servers reported identical NS records.
Each name server should return identical NS records.
Check for Lame Name servers
OK.
No lame name servers found. All of your name servers are configured to be either master or slave for your domain.
OK.
No private IPs found. Name servers using private IPs
can't be reached from the Internet causing DNS delays.
Name Servers Have A Records
OK.
Found A records for each name servers.
- a1-71.akam.net. → 193.108.91.71
- a12-65.akam.net. → 184.26.160.65
- a13-67.akam.net. → 2.22.230.67
- a14-67.akam.net. → 184.26.161.67
- a16-67.akam.net. → 23.211.132.67
- a7-64.akam.net. → 23.61.199.64
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
OK.
Found AAAA records for all name servers.
- a1-71.akam.net. → 2600:1401:2::47
- a12-65.akam.net. → 2600:1480:f000::41
- a13-67.akam.net. → 2600:1480:800::43
- a14-67.akam.net. → 2600:1480:1800::43
- a16-67.akam.net. → 2600:1406:1b::43
- a7-64.akam.net. → 2600:1406:32::40
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Name Servers Have Valid Names
OK.
All names are valid.
Name server name should be a valid host name, no partial name or IP address.
Check for Stealth Name Servers
OK.
No stealth name servers found.
All name servers returned by domain name servers should be listed at parent servers.
Check for Missing Name Servers
OK.
No missing name servers found.
All name servers returned by the parent name servers should have an NS record at your name servers.
OK.
No CNAMEs found in NS records.
RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)
and must not point to any CNAME records.
RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)
it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with
NS and MX records.
Despite this restrictions, there are many working configuration using CNAME with
NS and MX records.
OK.
All name servers are allowing TCP connections.
When response to a DNS query exceeds 512 bytes, TCP is negotiated
and used, all name servers should allow TCP connections (port 53).
Name Servers Distributed on Multiple Networks
OK.
Name servers are dispersed on 6
different C class networks:
-
184.26.160.0/24:
-
184.26.161.0/24:
-
193.108.91.0/24:
-
2.22.230.0/24:
-
23.211.132.0/24:
-
23.61.199.0/24:
Name servers should be dispersed (topologically and geographically)
across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Distributed on Multiple ASNs
OK.
Name servers are dispersed on 2
different Autonomous Systems:
-
AS20940:
-
AS21342:
- a1-71.akam.net.
- a12-65.akam.net.
- a13-67.akam.net.
- a14-67.akam.net.
- a16-67.akam.net.
- a7-64.akam.net.
Name servers should be dispersed (topologically and geographically)
across the Internet to avoid risk of single point of failure (RFC 2182).
WARNING:
Name servers software versions are exposed:
- 184.26.160.65: "45416.10"
- 184.26.161.67: "42475.168"
- 193.108.91.71: "41830.38"
- 2.22.230.67: "17146.38"
- 23.211.132.67: "29485.38"
- 23.61.199.64: "46499.7"
- 2600:1401:2::47: "23608.158"
- 2600:1406:1b::43: "35411.6"
- 2600:1406:32::40: "46499.4"
- 2600:1480:1800::43: "46807.209"
- 2600:1480:800::43: "35409.196"
- 2600:1480:f000::41: "45416.7"
Exposing name server's versions may be risky, when a new vulnerability is found
your name servers may be automatically exploited by
script kiddies
until you patch the system.
Learn how to hide version.
Domain SOA Record:
- Primary nameserver: a1-71.akam.net.
- Hostmaster (e-mail): hostmaster.akamai.com.
- Serial: 2019121901
- Refresh: 10800
- Retry: 300
- Expire: 604800
- Minimum TTL: 120
Name Servers Agreement on Serial Number
OK.
All name servers (6) have the same
serial number [2019121901].
Having different serials on your name servers may show inconsistencies between name servers
configuration (multiple masters), or communication errors (ACL and firewall issues).
OK.
Serial number format OK [2019121901].
Your serial number is following general convention for
serial number YYYYMMDDnn, where YYYY is four-digit year
number, MM is the month, DD is the day and nn is the
sequence number in case zone file is updated more
than once per day.
OK.
Primary name server is a1-71.akam.net. and is listed at the parent name servers.
The MNAME field defines the Primary Master name server for the zone,
this name server should be found in your NS records.
OK.
Contact email for DNS problems is
[email protected]. (
hostmaster.akamai.com.).
RNAME field defines an administrative email for your zone. RFC2142 recommends using
hostmaster
e-mail for this purpose, but any valid e-mail address can be used.
OK.
Refresh interval is 10800.
Recommended values [1200 .. 43200] (20 min ... 12 hours).
Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.
OK.
Retry interval is 300.
Recommended values [120 .. 7200] (2 minutes .. 2 hours).
Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.
OK.
Expire interval is 604800.
Recommended values [604800 .. 1209600] (1 week ... 2 weeks).
Expiry defines zone expiration time in seconds after which slave must re-validate zone file,
if contacting master fails then slave will stop responding to any queries.
WARNING:
Minimum TTL value is 120.
Recommended values [3600 .. 86400] (1 hour ... 1 day).
Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves
to cache negative responses.
Your name servers returned
2 MX records:
-
10 mxb-00185201.gslb.pphosted.com. TTL=60
-
10 mxa-00185201.gslb.pphosted.com. TTL=60
OK.
All name servers returned identical MX records.
Mail Servers Have A Records
OK.
Found A records for all mail servers.
- mxa-00185201.gslb.pphosted.com. → 67.231.157.53
- mxb-00185201.gslb.pphosted.com. → 67.231.157.53
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records
NOTICE:
While reading domain NS records at parent mail servers,
we found mail servers without AAAA records.
- mxa-00185201.gslb.pphosted.com. → ?
- mxb-00185201.gslb.pphosted.com. → ?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
OK.
All mail servers have reverse DNS entries configured correctly.
|
Server |
IP |
PTR (Reverse) |
IPs |
|
mxb-00185201.gslb.pphosted.com. |
67.231.157.53 |
mx0b-00185201.pphosted.com. |
67.231.157.53 |
|
mxa-00185201.gslb.pphosted.com. |
67.231.157.53 |
mx0b-00185201.pphosted.com. |
67.231.157.53 |
All mail servers should have a reverse DNS (PTR) entry for
each IP address (RFC 1912). Missing reverse DNS entries will
make many mail servers to reject your e-mails or mark them
as SPAM.
All IP's reverse DNS entries should resolve back to
IP address (IP → PTR → IP).
Many mail servers are configured to reject e-mails from
IPs with inconsistent reverse DNS configuration.
Check MX Records for Invalid Chars
OK.
No invalid characters found.
Name field from MX records should be a valid host name.
Check MX Records IPs are Public
OK.
No private IPs found.
Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.
Check MX Records for Duplicates
WARNING:
MX records duplicates (same IP address):
- 67.231.157.53: [mxa-00185201.gslb.pphosted.com. mxb-00185201.gslb.pphosted.com.]
Although technically valid, duplicate MX records have no benefits and can cause confusion.
Only Host Names in MX Records
OK.
No IPs found in MX records.
IP addresses are not allowed in MX records, only host names.
OK.
No CNAMEs found in MX records.
RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)
and must not point to any CNAME records.
RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)
it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with
NS and MX records.
Despite this restrictions, there are many working configuration using CNAME with
NS and MX records.
OK.
Mail servers IPs are not blacklisted.
Check Google Apps Settings
Test ignored, domain is not using Google Apps.
FAIL:
Connection to all mail servers failed.
- mxa-00185201.gslb.pphosted.com.:
Server checks disabled due complaints.
- mxb-00185201.gslb.pphosted.com.:
Server checks disabled due complaints.
To receive emails, mail servers should allow TCP connections on port 25.
OK.
No differences between mail server host names and greeting host name.
Accepts Postmaster Address
Temporary error, could not determine if
all mail servers are accepting emails to
[email protected] address:
RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster.
To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.
Temporary error, could not determine if
all mail servers are accepting emails to
[email protected] address:
RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster.
To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.
WARNING:
Domain doesn't have SPF record.
SPF
(Sender Policy Framework) record is designed to prevent e-mail spoofing.
Typical SPF record would be:
v=spf1 a mx ~all
or
v=spf1 a mx include:_spf.google.com ~all if you are using Google Apps.
FAIL:
Your name servers returned different TXT records:
- 184.26.160.65 → z71y4tw115z24yjmztfck4sdf82dmqq5
intersight=
bb27f6436d17dd58f6d584018feab5eac4599bda4fcec75a6e4fa62bde831b62
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
facebook-domain-verification=yhbi2knspjl0pp598jps2e9yqiuzqe
onetrust-domain-verification=16f9a908a417496d9ad7946192d18c97
adobe-idp-site-verification=19268c957df4a1a3ad016dda9890a54175d302768eb33d318e103880a8bd411f
- 184.26.161.67 → docusign=d53ea727-cf7f-4c4c-b79c-c3c4420c1ee5
bjs.com=hvs5mdjzmh7nvsgttdxdlz16cx2qqqwl
adobe-idp-site-verification=19268c957df4a1a3ad016dda9890a54175d302768eb33d318e103880a8bd411f
onetrust-domain-verification=16f9a908a417496d9ad7946192d18c97
MS=ms95009833
apple-domain-verification=EHs1l5GZifslTsMd
00nhpcp57nc1txpn2hlw8gw3k0pdwnhd
2qk51v4778vj2nf9lfnv2b3stnvmv0dj
- 193.108.91.71 → facebook-domain-verification=yhbi2knspjl0pp598jps2e9yqiuzqe
vc9s4m3xjxn3zn39rztmkb2r09xy0bxt
atlassian-domain-verification=EMus5LvCBbSIR/kQV4b8sJRrZszlmXdQaFUo9GXsFONUQ3nXGKCLLBonraLIMjBv
+AEwY8OO3mwdkKCICOfxUe6a646DXJNGgB5KabbtL/fl0qkQ21jf+5m8ZJWRp+UqlpO0xhtYwSegNkUxRC9ZHw==
safetyculture-domain-verification=51118735-3321-4a56-b282-ad2dc2d38540
MS=ms91334944
bjs.com=hvs5mdjzmh7nvsgttdxdlz16cx2qqqwl
- 2.22.230.67 → docusign=31a4b16f-5c2f-4e56-9fdc-ee1dd06b5bf2
bjs.com=hvs5mdjzmh7nvsgttdxdlz16cx2qqqwl
MS=ms95009833
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
google-site-verification=M8MnRoJEQjccNyiAJleUnWg9qDhNJdKklYetlqPSL3c
ibmid=f6d6dbae-6172-4cee-af88-0fc3ecb140df
apple-domain-verification=EHs1l5GZifslTsMd
docusign=d53ea727-cf7f-4c4c-b79c-c3c4420c1ee5
- 23.211.132.67 → docusign=d53ea727-cf7f-4c4c-b79c-c3c4420c1ee5
vc9s4m3xjxn3zn39rztmkb2r09xy0bxt
adobe-idp-site-verification=19268c957df4a1a3ad016dda9890a54175d302768eb33d318e103880a8bd411f
facebook-domain-verification=yhbi2knspjl0pp598jps2e9yqiuzqe
intersight=
bb27f6436d17dd58f6d584018feab5eac4599bda4fcec75a6e4fa62bde831b62
docusign=31a4b16f-5c2f-4e56-9fdc-ee1dd06b5bf2
- 23.61.199.64 → z71y4tw115z24yjmztfck4sdf82dmqq5
atlassian-domain-verification=EMus5LvCBbSIR/kQV4b8sJRrZszlmXdQaFUo9GXsFONUQ3nXGKCLLBonraLIMjBv
+AEwY8OO3mwdkKCICOfxUe6a646DXJNGgB5KabbtL/fl0qkQ21jf+5m8ZJWRp+UqlpO0xhtYwSegNkUxRC9ZHw==
bjs.com=hvs5mdjzmh7nvsgttdxdlz16cx2qqqwl
facebook-domain-verification=6leb5xf6faejzf2ls9xfkj0l6ztzfb
facebook-domain-verification=yhbi2knspjl0pp598jps2e9yqiuzqe
Only SPF records are compared, all name servers should return identical SPF records.
No SPF type records found.
All name servers should return identical SPF records.
OK.
Found DMARC record:
DMARC
(Domain-based Message Authentication, Reporting & Conformance)
helps reducing potential of email-based abuse such as spam and
phishing e-mails.
OK.
Domain
bjs.com. resolves to:
Domain Name IPs are Public
OK.
No private IPs found for bjs.com..
Web servers using private IPs can't be reached from the Internet.
OK.
Domain
www.bjs.com. resolves to:
OK.
No private IPs found for www.bjs.com..
Web servers using private IPs can't be reached from the Internet.
Report completed in 1.03 seconds.
Recent reports:
hostait.us
vegaluralimentaria.com
magictechinc.com
hostait.com
hostait.com