Report for hpweb.com.br
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
c.dns.br.).
Domain NS records:
-
ns1.hpweb.com.br. TTL=3600
[187.108.196.96]
[NO GLUE6]
-
ns2.hpweb.com.br. TTL=3600
[187.108.196.97]
[NO GLUE6]
OK.
Parent name servers are offering glue for domain's name
servers. We received name servers list and it's IP addresses
from parent name server (c.dns.br.).
Name Servers Have A Records
OK.
Found A records for all name servers.
- ns1.hpweb.com.br. → 187.108.196.96
- ns2.hpweb.com.br. → 187.108.196.97
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
NOTICE:
While reading domain NS records at parent name servers,
we found name servers without AAAA records.
- ns1.hpweb.com.br. → ?
- ns2.hpweb.com.br. → ?
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Your name servers returned
2 NS records:
-
ns1.hpweb.com.br. TTL=86400
[187.108.196.96]
[NO GLUE6]
-
ns2.hpweb.com.br. TTL=86400
[187.108.196.97]
[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 2 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.
- ns1.hpweb.com.br. → 187.108.196.96
- ns2.hpweb.com.br. → 187.108.196.97
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
NOTICE:
We found name servers without AAAA records.
- ns1.hpweb.com.br. → ?
- ns2.hpweb.com.br. → ?
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
WARNING:
All name servers are located in one C class network:
-
187.108.196.0/24:
- ns1.hpweb.com.br.
- ns2.hpweb.com.br.
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
WARNING:
All name servers are located in one Autonomous System:
-
AS53107:
- ns1.hpweb.com.br.
- ns2.hpweb.com.br.
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:
- 187.108.196.96: "PowerDNS Authoritative Server 4.9.2 (built Oct 8 2024 14:45:11 by [email protected])"
- 187.108.196.97: "PowerDNS Authoritative Server 4.9.2 (built Oct 8 2024 14:45:11 by [email protected])"
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: ns1.hpweb.com.br.
- Hostmaster (e-mail): root.linux.hpweb.com.br.
- Serial: 2024112312
- Refresh: 3600
- Retry: 1800
- Expire: 1209600
- Minimum TTL: 86400
Name Servers Agreement on Serial Number
OK.
All name servers (2) have the same
serial number [2024112312].
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 [2024112312].
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 ns1.hpweb.com.br. 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]. (
root.linux.hpweb.com.br.).
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 3600.
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 1800.
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 1209600.
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.
OK.
Minimum TTL value is 86400.
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
1 MX records:
-
0 hpweb.com.br. TTL=14400
OK.
All name servers returned identical MX records.
Mail Servers Have A Records
OK.
Found A records for all mail servers.
- hpweb.com.br. → 187.108.196.90
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.
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
WARNING:
Found mail servers with inconsistent reverse DNS entries.
You should fix them if you are using those servers to send email.
|
Server |
IP |
PTR (Reverse) |
IPs |
|
hpweb.com.br. |
187.108.196.90 |
sp-187-108-196-90.l3.eveocloud.net. |
? |
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
OK.
No MX records duplicates (same IP addresses) found.
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.
Could not get MX records from your name servers.
OK.
Domain
hpweb.com.br. resolves to:
Domain Name IPs are Public
OK.
No private IPs found for hpweb.com.br..
Web servers using private IPs can't be reached from the Internet.
OK.
Domain
www.hpweb.com.br. resolves to:
OK.
No private IPs found for www.hpweb.com.br..
Web servers using private IPs can't be reached from the Internet.
Report completed in 1.48 seconds.
Recent reports:
gojek.com
gojek.co.id
media-handwerk.at
gojek.com
gozenhosting.com