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



X

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

Checked:
14.09.2021 22:54:59


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
1cs.argasmo.ru

Name Error
yes
1
0
www.1cs.argasmo.ru

Name Error
yes
1
0
*.argasmo.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.1cs.argasmo.ru
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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2021, 00:00:00 +, Signature-Inception: 09.09.2021, 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: ru
ru
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 7729, DigestType 2 and Digest wDWHERO7fHDB+/wcm/36l4FzM0jVT375pK0CGqADNvM=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.09.2021, 17:00:00 +, Signature-Inception: 14.09.2021, 16:00:00 +, KeyTag 26838, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 51699, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 02.10.2021, 00:00:00 +, Signature-Inception: 12.09.2021, 00:00:00 +, KeyTag 7729, Signer-Name: ru



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



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

Zone: argasmo.ru
argasmo.ru
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 "nivihd5abg760f24affudf3kt7b1u1a3" between the hashed NSEC3-owner "niua7vejultm1h822m6v30adco1q2jqa" and the hashed NextOwner "nj3gkjgb4ikjij2uvhvqht7bg6a93j5l". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner niua7vejultm1h822m6v30adco1q2jqa.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.10.2021, 21:37:53 +, Signature-Inception: 03.09.2021, 12:16:50 +, KeyTag 51699, Signer-Name: ru



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tdui9d4jkuds8b9t86gj39pgflcnlgm5" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "te33kgtaqu9m5crq3ibsilqu11gfgttt". So that domain name is the Closest Encloser of "argasmo.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tdui9d4jkuds8b9t86gj39pgflcnlgm5.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.10.2021, 10:26:34 +, Signature-Inception: 03.09.2021, 12:16:50 +, KeyTag 51699, Signer-Name: ru



0 DNSKEY RR found




Zone: 1cs.argasmo.ru
1cs.argasmo.ru
0 DS RR in the parent zone found

Zone: www.1cs.argasmo.ru
www.1cs.argasmo.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.1cs.argasmo.ru
  ns1.beget.com

1cs.argasmo.ru
  ns1.beget.com

argasmo.ru
  ns1.beget.com
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns1.beget.pro
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns1.beget.ru
5.101.159.11
St Petersburg/St.-Petersburg/Russia (RU) - Geo location BEGET.RU


  ns2.beget.com
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC


  ns2.beget.pro
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC


  ns2.beget.ru
185.50.27.12
St Petersburg/St.-Petersburg/Russia (RU) - Beget LLC

ru
  a.dns.ripn.net / tau.ripn.net


  b.dns.ripn.net


  d.dns.ripn.net


  e.dns.ripn.net / gamma-ams.ripn.net


  f.dns.ripn.net / tau-sin.ripn.net


4. SOA-Entries


Domain:ru
Zone-Name:ru
Primary:a.dns.ripn.net
Mail:hostmaster.ripn.net
Serial:4048444
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:argasmo.ru
Zone-Name:argasmo.ru
Primary:ns1.beget.com
Mail:hostmaster.beget.com
Serial:1616767213
Refresh:300
Retry:600
Expire:86400
TTL:300
num Entries:6


Domain:1cs.argasmo.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.1cs.argasmo.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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







7. Comments


1. General Results, most used to calculate the result

Aname "1cs.argasmo.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 1803 (complete: 168171)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AInfo:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.beget.com (5.101.159.11), ns1.beget.pro (5.101.159.11), ns2.beget.com (185.50.27.12), ns2.beget.pro (185.50.27.12)
AGood (1 - 3.0):: An average of 2.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 6 different Name Servers found: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru, 4 Name Servers included in Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, 6 Name Servers included in 1 Zone definitions: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru, 1 Name Servers listed in SOA.Primary: ns1.beget.com.
AGood: Only one SOA.Primary Name Server found.: ns1.beget.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.beget.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.com (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.pro (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.beget.ru (5.101.159.11): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.com (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.pro (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.beget.ru (185.50.27.12): Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, Zone: ns1.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru. Name Servers defined in Zone, missing in Delegation: ns1.beget.ru, ns2.beget.ru.
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.
AInfo: Ipv4-Subnet-list: 6 Name Servers, 2 different subnets (first Byte): 185., 5., 2 different subnets (first two Bytes): 185.50., 5.101., 2 different subnets (first three Bytes): 185.50.27., 5.101.159.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.beget.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.beget.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
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

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: 42740 milliseconds, 42.740 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" > 2019 are listed

No CRT - CT-Log entries found


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.beget.com, ns1.beget.pro, ns1.beget.ru, ns2.beget.com, ns2.beget.pro, ns2.beget.ru

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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.beget.com: 5.101.159.11
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: ns2.beget.com
185.50.27.12
3
pro
NS
l.root-servers.net (2001:500:9f::42)

Answer: a0.pro.afilias-nst.info, a2.pro.afilias-nst.info, b0.pro.afilias-nst.org, b2.pro.afilias-nst.org, c0.pro.afilias-nst.info, d0.pro.afilias-nst.org
4
ns1.beget.pro: 5.101.159.11
NS
a0.pro.afilias-nst.info (2001:500:c0::1)

Answer: ns2.beget.pro
185.50.27.12
5
ru
NS
i.root-servers.net (2001:7fe::53)

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
6
ns1.beget.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
7
ns2.beget.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
8
RU
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
9
ns1.beget.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12
10
ns2.beget.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.beget.RU, ns2.beget.RU

Answer: ns1.BEGET.RU
5.101.159.11

Answer: ns2.BEGET.RU
185.50.27.12


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
argasmo.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
argasmo.ru
v=spf1 redirect=beget.com
ok
1
0
_acme-challenge.1cs.argasmo.ru.argasmo.ru

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=8995f9f9-1df8-4f9d-a542-e5fcddfe3996


Last Result: https://check-your-website.server-daten.de/?q=1cs.argasmo.ru - 2021-09-14 22:54:59


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

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