DNS report for gurkhasekta.com.hk

This report was generated 1 week ago. Refresh?
B
Connectivity
100%
Performance
80%
Resilience & Security
75%
DNS records
100%
Proud of your DNS score? Share it with the world!

Connectivity: 100%

The following nameservers are available and responding correctly for DNS queries for your domain gurkhasekta.com.hk.

Nameserver IP address(es) SOA serial
ns31.cloudns.net. 109.201.133.111
2a00:1768:1001:9::31:1
2019120316
ns32.cloudns.net. 209.58.140.85
2605:fe80:2100:a013:7::1
2019120316
ns33.cloudns.net. 54.36.26.145 2019120316
ns34.cloudns.net. 185.206.180.104
2a0b:1640:1:1:1:1:8ec:5a47
2019120316

Good news, no warnings or errors were found.

We could not find any recommendations at this time.

Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.

  • All nameservers reply with the same SOA serial number.
  • The nameserver IPs are distributed across multiple subnets.
  • All nameservers are online.
  • Nameservers are available over IPv4.
  • Nameservers are available over IPv6.

Performance: 80%

We tested each nameserver and measured the following response times.

Nameserver IP address(es) Response time
ns31.cloudns.net. 109.201.133.111
2a00:1768:1001:9::31:1
7ms
timeout
ns32.cloudns.net. 209.58.140.85
2605:fe80:2100:a013:7::1
146ms
151ms
ns33.cloudns.net. 54.36.26.145 9ms
ns34.cloudns.net. 185.206.180.104
2a0b:1640:1:1:1:1:8ec:5a47
14ms
13ms

We detected the following errors or warnings about your DNS configuration. These caused your DNS rating to be lowered. Resolving these will grant a higher DNS Spy rating for your domain.

  • Nameserver ns31.cloudns.net. (2a00:1768:1001:9::31:1) did not respond.
  • Nameserver ns32.cloudns.net. (2605:fe80:2100:a013:7::1) replied, but took too long (151ms). This will severely impact performance.

We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.

  • Nameserver ns32.cloudns.net. (209.58.140.85) replied reasonably fast (< 150ms), but you should aim for < 50ms response times.

Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.

  • Nameserver ns31.cloudns.net. (109.201.133.111) replied quickly (< 50ms).
  • Nameserver ns33.cloudns.net. (54.36.26.145) replied quickly (< 50ms).
  • Nameserver ns34.cloudns.net. (185.206.180.104) replied quickly (< 50ms).
  • Nameserver ns34.cloudns.net. (2a0b:1640:1:1:1:1:8ec:5a47) replied in a reasonable time.

Resilience & Security: 75%

These are the locations and providers of your nameservers.

Nameserver Location ISP
ns31.cloudns.net. IPv4: NL
IPv6: NL
AS43350 - NFORCE, NL
AS43350 - NFORCE, NL
ns32.cloudns.net. IPv4: US
IPv6: US
AS7203 - LEASEWEB-USA-SFO-12 - Leaseweb USA, Inc., US
AS7203 - LEASEWEB-USA-SFO-12 - Leaseweb USA, Inc., US
ns33.cloudns.net. IPv4: FR AS16276 - OVH, FR
ns34.cloudns.net. IPv4: BG
IPv6: BG
AS205787 - PUBLICLOUD, BG
AS205787 - PUBLICLOUD, BG

We detected the following errors or warnings about your DNS configuration. These caused your DNS rating to be lowered. Resolving these will grant a higher DNS Spy rating for your domain.

  • No DNSSEC records found. Consider enabling DNSSEC, as it provides a way to validate DNS responses for data integrity.
  • All the nameservers are being operated from a single domain (cloudns.net). If that domain gets compromised or goes offline, the DNS will be unavailable. Consider spreading the nameservers across multiple domains.

We could not find any recommendations at this time.

Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.

  • You have more than 1 nameserver.
  • The IPv4 nameservers are distributed among multiple providers.
  • The IPv4 nameservers are distributed across multiple locations.
  • The IPv6 nameservers are distributed among multiple providers.
  • The IPv6 nameservers are distributed across multiple locations.
  • CAA records found.

DNS records: 100%

Our scans detected the following publicly available DNS records.

Record TTL Value
CAA gurkhasekta.com.hk 1h 0 issue "letsencrypt.org"
MX gurkhasekta.com.hk 1h 1 aspmx.l.google.com.
10 alt3.aspmx.l.google.com.
10 alt4.aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
NS gurkhasekta.com.hk 1h ns31.cloudns.net.
ns32.cloudns.net.
ns33.cloudns.net.
ns34.cloudns.net.
SOA gurkhasekta.com.hk 1h ns31.cloudns.net. support.cloudns.net. 2019120316 7200 1800 1209600 3600
TXT gurkhasekta.com.hk 1h "v=spf1 include:_spf.google.com ~all"

Good news, no warnings or errors were found.

We detected some possible recommendations for you to consider. No penalties were given for these, but resolving them can give you a higher DNS score.

  • No DMARC records have been found. Consider configuring DMARC for improved e-mail authentication.
  • No DNS record found on your zone apex (gurkhasekta.com.hk). Consider adding a DNS record for "gurkhasekta.com.hk" as an A record.
  • No IPv6 record has been found on the zone apex (gurkhasekta.com.hk). Consider enabling IPv6 in the infrastructure by adding an AAAA record on this domain.

Good news, we detected the following achievements in your DNS configuration. Each of these checks has increased your DNS Spy score.

  • Multiple MX records found.
  • MX records with different priorities found (main + fall-back mailservers).
  • The MX record for "gurkhasekta.com.hk" has a long TTL (1h+).
  • The MX records points to multiple mailservers.
  • The NS records have a long TTL (1h+).
  • Your SOA serial number follows the best practice YYYYMMDDxx format.
  • SPF records have been found.
  • SPF records are set up restrictively.
  • The active nameservers match the NS records.
  • The DNS records appear to be RFC compliant.
Proud of your DNS score? Share it with the world!

 

Have a look at other public DNS scans.