Check DNS, Urls + Redirects, Certificates and Content of your Website



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
23.09.2022 06:14:48


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
dialoguegroup.net
A
103.78.208.69
Cipadung/West Java/Indonesia (ID) - MORATELINDO
No Hostname found
yes
1
0

AAAA

yes


www.dialoguegroup.net


yes
2
1
www.dialoguegroup.net
A
103.78.208.69
Cipadung/West Java/Indonesia (ID) - MORATELINDO
No Hostname found
no


*.dialoguegroup.net
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 18733, Flags 256



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 20826, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 10.10.2022, 00:00:00 +, Signature-Inception: 19.09.2022, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: net
net
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.10.2022, 16:00:00 +, Signature-Inception: 22.09.2022, 15:00:00 +, KeyTag 20826, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20826 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 4403, Flags 256



Public Key with Algorithm 8, KeyTag 35886, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 16:28:30 +, Signature-Inception: 21.09.2022, 16:23:30 +, KeyTag 35886, Signer-Name: net



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35886 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest "eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: dialoguegroup.net
dialoguegroup.net
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "lou02nb1sd1odrb7uccp5aoq2dniii11" between the hashed NSEC3-owner "lotvdg12a729fnl0grf5ccs33ctom2dg" and the hashed NextOwner "lou0ft9eq3i249vggbcco2amdkfkkhs7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner lotvdg12a729fnl0grf5ccs33ctom2dg.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 27.09.2022, 06:21:33 +, Signature-Inception: 20.09.2022, 05:11:33 +, KeyTag 4403, Signer-Name: net



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "dialoguegroup.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2022, 06:22:24 +, Signature-Inception: 21.09.2022, 05:12:24 +, KeyTag 4403, Signer-Name: net



0 DNSKEY RR found




Zone: www.dialoguegroup.net
www.dialoguegroup.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.dialoguegroup.net
  ns1.rcs-server.net

dialoguegroup.net
  ns1.rcs-server.net
203.161.184.28
Pandeyan/Yogyakarta/Indonesia (ID) - JOGJACAMP


 
54.251.110.33
Singapore/Central Singapore/Singapore (SG) - Amazon.com, Inc.


U  ns2.rcs-server.net
54.251.110.65
Singapore/Central Singapore/Singapore (SG) - Amazon.com, Inc.

net
  a.gtld-servers.net / nnn1-par6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-lon5


  k.gtld-servers.net / nnn1-lon5


  l.gtld-servers.net / nnn1-lon5


  m.gtld-servers.net / nnn1-lon5


4. SOA-Entries


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1663906462
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1663906477
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:dialoguegroup.net
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:dialoguegroup.net
Zone-Name:dialoguegroup.net
Primary:ns1.rcs-server.net
Mail:domain.riaucybersolution.net
Serial:2022090608
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
num Entries:2


Domain:www.dialoguegroup.net
Zone-Name:dialoguegroup.net
Primary:ns1.rcs-server.net
Mail:domain.riaucybersolution.net
Serial:2022090608
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://dialoguegroup.net/
103.78.208.69
-14

10.050
T
Timeout - The operation has timed out

• http://www.dialoguegroup.net/
103.78.208.69
-14

10.027
T
Timeout - The operation has timed out

• https://dialoguegroup.net/
103.78.208.69
-14

10.017
T
Timeout - The operation has timed out

• https://www.dialoguegroup.net/
103.78.208.69
-14

10.016
T
Timeout - The operation has timed out

• http://dialoguegroup.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
103.78.208.69
-14

10.037
T
Timeout - The operation has timed out
Visible Content:

• http://www.dialoguegroup.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
103.78.208.69
-14

10.057
T
Timeout - The operation has timed out
Visible Content:

• https://103.78.208.69/
103.78.208.69
-14

10.036
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "dialoguegroup.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 7665 (complete: 199710)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: dialoguegroup.net has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: dialoguegroup.net has no ipv6 address.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
XFatal error: Nameserver doesn't support TCP connection: ns2.rcs-server.net / 54.251.110.65: Timeout
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain dialoguegroup.net, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 3 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.rcs-server.net, ns2.rcs-server.net, 2 Name Servers included in Delegation: ns1.rcs-server.net, ns2.rcs-server.net, 2 Name Servers included in 2 Zone definitions: ns1.rcs-server.net, ns2.rcs-server.net, 1 Name Servers listed in SOA.Primary: ns1.rcs-server.net.
AGood: Only one SOA.Primary Name Server found.: ns1.rcs-server.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.rcs-server.net.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: rcs-server.net
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: ID, SG
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 203., 54., 2 different subnets (first two Bytes): 203.161., 54.251., 2 different subnets (first three Bytes): 203.161.184., 54.251.110.
AGood: Name Server IPv4-addresses from different subnet found:
Nameserver doesn't pass all EDNS-Checks: ns1.rcs-server.net: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns2.rcs-server.net / 54.251.110.65: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

http://dialoguegroup.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.78.208.69
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.dialoguegroup.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.78.208.69
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 185600 milliseconds, 185.600 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
0
2
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
0
0
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6772566486
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-21 03:13:24
2022-08-19 03:13:23
dialoguegroup.net
1 entries


6772211585
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-05-21 01:47:47
2022-08-19 01:47:46
dialoguegroup.net
1 entries


6218595435
precert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2022-02-20 23:00:00
2022-05-22 21:59:59
dialoguegroup.net, www.dialoguegroup.net
2 entries


5638130915
precert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2021-11-18 23:00:00
2022-02-17 22:59:59
dialoguegroup.net, www.dialoguegroup.net
2 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.rcs-server.net, ns2.rcs-server.net

QNr.DomainTypeNS used
1
net
NS
g.root-servers.net (2001:500:12::d0d)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.rcs-server.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: cl1.rcs-server.net, cl2.rcs-server.net, cl3.rcs-server.net, cl4.rcs-server.net

Answer: cl1.rcs-server.net
139.99.85.114

Answer: cl2.rcs-server.net
103.120.205.99

Answer: cl3.rcs-server.net
103.120.65.174

Answer: cl4.rcs-server.net
103.120.204.54
3
ns2.rcs-server.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: cl1.rcs-server.net, cl2.rcs-server.net, cl3.rcs-server.net, cl4.rcs-server.net

Answer: cl1.rcs-server.net
139.99.85.114

Answer: cl2.rcs-server.net
103.120.205.99

Answer: cl3.rcs-server.net
103.120.65.174

Answer: cl4.rcs-server.net
103.120.204.54
4
ns1.rcs-server.net: 203.161.184.28, 54.251.110.33
A
cl1.rcs-server.net (139.99.85.114)
5
ns1.rcs-server.net: No AAAA record found
AAAA
cl1.rcs-server.net (139.99.85.114)
6
ns2.rcs-server.net: 54.251.110.65
A
cl1.rcs-server.net (139.99.85.114)
7
ns2.rcs-server.net: No AAAA record found
AAAA
cl1.rcs-server.net (139.99.85.114)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.dialoguegroup.net
0

no CAA entry found
1
0
dialoguegroup.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dialoguegroup.net
google-site-verification=5Bok2gj9ZRD5wVB1wWiUs2f7EUR7qetsW5e6qYwdH9s
ok
1
0
dialoguegroup.net
v=spf1 a:dialoguegroup.net ip4:103.78.208.70 ip4:27.50.30.228 include:_spf.oxygen.id ~all
ok
1
0
www.dialoguegroup.net

ok
1
0
_acme-challenge.dialoguegroup.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.dialoguegroup.net

Name Error - The domain name does not exist
1
0
_acme-challenge.dialoguegroup.net.dialoguegroup.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.dialoguegroup.net.dialoguegroup.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.dialoguegroup.net.www.dialoguegroup.net

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

dialoguegroup.net
0
mail.dialoguegroup.net
0
1
ok


A


103.78.208.70
0
1
ok


CNAME



0
0
ok



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=2d1bedc2-cef6-4949-b07b-a25f890b9cd5


Last Result: https://check-your-website.server-daten.de/?q=dialoguegroup.net - 2022-09-23 06:14:48


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=dialoguegroup.net" target="_blank">Check this Site: dialoguegroup.net</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro