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

...

skip EDNS-Check

skip Content-Check

check links

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

Checked:
20.11.2023 10:07:11

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
owa.mcc.rsa.ru	A	46.61.181.111 Perm/Perm Krai/Russia (RU) - JSC TsNIIMash Hostname: owa.mcc.rsa.ru	yes	1	0
	AAAA		yes
www.owa.mcc.rsa.ru		Name Error	yes	1	0
*.mcc.rsa.ru	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.owa.mcc.rsa.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 46780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2023, 00:00:00 +, Signature-Inception: 20.11.2023, 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 18274, DigestType 2 and Digest qzXRfT8560LO4UxicyR5ONM+7qqfXKpws4WNv0vT6Hs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.12.2023, 05:00:00 +, Signature-Inception: 20.11.2023, 04:00:00 +, KeyTag 46780, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 44301, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 07.12.2023, 00:00:00 +, Signature-Inception: 17.11.2023, 00:00:00 +, KeyTag 18274, Signer-Name: ru


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


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

Zone: rsa.ru
rsa.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 "b9djnrktk9s0tamad9q8dcdil9q2na7i" between the hashed NSEC3-owner "b9ddols1o5m6l4ml5on1knqmfetpbot4" and the hashed NextOwner "b9ftfgingev3umhefdb6frb1uomrg9qn". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner b9ddols1o5m6l4ml5on1knqmfetpbot4.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 21.12.2023, 01:18:30 +, Signature-Inception: 13.11.2023, 08:18:30 +, KeyTag 44301, Signer-Name: ru


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j20c0qkdhua3cumnkst289ff06u2sq91" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "j21c11shootmoeqkprm91c8agl4886m6". So that domain name is the Closest Encloser of "rsa.ru". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner j20c0qkdhua3cumnkst289ff06u2sq91.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 21.12.2023, 18:56:26 +, Signature-Inception: 13.11.2023, 08:18:30 +, KeyTag 44301, Signer-Name: ru


	0 DNSKEY RR found




Zone: mcc.rsa.ru
mcc.rsa.ru	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: owa.mcc.rsa.ru
owa.mcc.rsa.ru	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.owa.mcc.rsa.ru
www.owa.mcc.rsa.ru	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.owa.mcc.rsa.ru	• ns3-l2.nic.ru
owa.mcc.rsa.ru	• ns3-l2.nic.ru / nscache-ct03.prod.int.nic.ru	193.232.146.1 Moscow/Russia (RU) - JSC "RU-CENTER"	•
mcc.rsa.ru	• ns3-l2.nic.ru / nscache-ct03.prod.int.nic.ru	193.232.146.1 Moscow/Russia (RU) - JSC "RU-CENTER"	•
rsa.ru	• ns3-l2.nic.ru / nscache-ct03.prod.int.nic.ru	193.232.146.1 Moscow/Russia (RU) - JSC "RU-CENTER"	•
	• ns3-l5.nic.ru / ns3-l5.nic.ru	193.232.146.13 Moscow/Russia (RU) - JSC "RU-CENTER"
	• ns4-cloud.nic.ru / nscloud1-1.reg.ru	89.104.93.30 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.93.33 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.93.34 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.30 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.33 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.34 Moscow/Russia (RU) - Ru-Center	•
	• ns4-l2.nic.ru / nscache-dp04.prod.int.nic.ru	91.217.20.20 Moscow/Russia (RU) - JSC "RU-CENTER"	•
	• ns4-l5.nic.ru / ns4-l5.nic.ru	91.217.20.13 Moscow/Russia (RU) - JSC "RU-CENTER"
	• ns8-cloud.nic.ru / nscloud1-5.reg.ru	89.104.93.31 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.93.35 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.93.36 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.31 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.35 Moscow/Russia (RU) - Ru-Center	•
	•	89.104.95.36 Moscow/Russia (RU) - Ru-Center	•
	• ns8-l2.nic.ru / nscache-spb02.prod.int.nic.ru	91.217.21.20 Moscow/Russia (RU) - JSC "RU-CENTER"	•
ru	• a.dns.ripn.net / tau-m9-ns5.ripn.net		•
	• b.dns.ripn.net / tau-std.ripn.net		•
	• d.dns.ripn.net / spb2-tau-01.ix.ru		•
	• e.dns.ripn.net / tau-ekt.ripn.net		•
	• f.dns.ripn.net / gamma-vlv.ripn.net		•

4. SOA-Entries

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

Domain:	rsa.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	2

Domain:	rsa.ru
Zone-Name:	rsa.ru
Primary:	ns3-l2.nic.ru
Mail:	root.mcc.rsa.ru
Serial:	2015121517
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	7200
num Entries:	15

Domain:	mcc.rsa.ru
Zone-Name:	rsa.ru
Primary:	ns3-l2.nic.ru
Mail:	root.mcc.rsa.ru
Serial:	2015121517
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	7200
num Entries:	1

Domain:	owa.mcc.rsa.ru
Zone-Name:	rsa.ru
Primary:	ns3-l2.nic.ru
Mail:	root.mcc.rsa.ru
Serial:	2015121517
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	7200
num Entries:	1

Domain:	www.owa.mcc.rsa.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

Domainname	Http-Status	Sec.	G
• http://owa.mcc.rsa.ru/ 46.61.181.111	-14	10.043	T
Timeout - The operation has timed out

• https://owa.mcc.rsa.ru/ 46.61.181.111	-14	10.046	T
Timeout - The operation has timed out

• http://owa.mcc.rsa.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.61.181.111	-14	10.046	T
Timeout - The operation has timed out
Visible Content:

• https://46.61.181.111/ 46.61.181.111	-14	10.030	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "owa.mcc.rsa.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: 2755 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: owa.mcc.rsa.ru 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: owa.mcc.rsa.ru has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "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.
X	Fatal error: Nameserver doesn't support TCP connection: ns3-l5.nic.ru / 193.232.146.13: Refused
X	Fatal error: Nameserver doesn't support TCP connection: ns4-l5.nic.ru / 91.217.20.13: Refused
	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 owa.mcc.rsa.ru, 1 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.owa.mcc.rsa.ru
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
A	Info:: 12 Queries complete, 12 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Info:: 7 different Name Servers found: ns3-l2.nic.ru, ns3-l5.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns4-l5.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru, 4 Name Servers included in Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, 5 Name Servers included in 2 Zone definitions: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru, 1 Name Servers listed in SOA.Primary: ns3-l2.nic.ru.
A	Good: Only one SOA.Primary Name Server found.: ns3-l2.nic.ru.
A	Good: SOA.Primary Name Server included in the delegation set.: ns3-l2.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3-l2.nic.ru (193.232.146.1): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.93.30): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.93.33): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.93.34): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.95.30): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.95.33): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-cloud.nic.ru (89.104.95.34): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4-l2.nic.ru (91.217.20.20): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.93.31): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.93.35): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.93.36): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.95.31): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.95.35): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-cloud.nic.ru (89.104.95.36): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
X	Fatal: 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns8-l2.nic.ru (91.217.21.20): Delegation: ns3-l2.nic.RU, ns3-l5.nic.ru, ns4-l5.nic.ru, ns8-l2.nic.RU, Zone: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru. Name Servers defined in Delegation, missing in Zone: ns3-l5.nic.ru, ns4-l5.nic.ru.Name Servers defined in Zone, missing in Delegation: ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 7 different Name Servers found
	Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 7 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.: 7 Name Servers, 1 Top Level Domain: ru
	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: nic.ru
	Warning: All Name Servers from the same Country / IP location.: 7 Name Servers, 1 Countries: RU
A	Info: Ipv4-Subnet-list: 17 Name Servers, 3 different subnets (first Byte): 193., 89., 91., 3 different subnets (first two Bytes): 193.232., 89.104., 91.217., 5 different subnets (first three Bytes): 193.232.146., 89.104.93., 89.104.95., 91.217.20., 91.217.21.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Good: Nameserver supports TCP connections: 1 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 1 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns3-l2.nic.ru: 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: ns3-l5.nic.ru / 193.232.146.13: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns3-l5.nic.ru). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns4-l5.nic.ru / 91.217.20.13: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns4-l5.nic.ru). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
A	Good: 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.
	4. Content- and Performance-critical Checks
	http://owa.mcc.rsa.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.61.181.111	-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.
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 410290 milliseconds, 410.290 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

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10359141728 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-08-21 03:13:02	2023-11-19 04:13:01	owa.mcc.rsa.ru 1 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: ns3-l2.nic.ru, ns3-l5.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns4-l5.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru

QNr.	Domain	Type	NS used
1	ru	NS	f.root-servers.net (2001:500:2f::f)
	Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
2	ns3-l2.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
3	ns3-l5.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
4	ns4-cloud.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
5	ns4-l2.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
6	ns4-l5.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
7	ns8-cloud.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
8	ns8-l2.nic.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
9	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
10	ns5.nic.RU	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
11	ns6.nic.RU	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
12	ns9.nic.RU	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU
	Answer: ns5.NIC.RU 2a02:2090:e800:9000:31:177:67:100, 31.177.67.100
	Answer: ns6.NIC.RU 2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100
	Answer: ns9.NIC.RU 2a02:2090:e400:7000:31:177:85:186, 31.177.85.186

13. CAA - Entries

Domainname	Value	∑ Queries
owa.mcc.rsa.ru	no CAA entry found	1
mcc.rsa.ru	no CAA entry found	1
rsa.ru	no CAA entry found	1
ru	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
mcc.rsa.ru	v=spf1 ip4:46.61.181.0/24 ~all	ok	1
owa.mcc.rsa.ru		ok	1
_acme-challenge.owa.mcc.rsa.ru	V5yw5GSCghQbpOCm8MZblIUAmBTorz0OY1j-1K-xU2E	looks good, correct length, correct characters	1
_acme-challenge.owa.mcc.rsa.ru.mcc.rsa.ru		Name Error - The domain name does not exist	1
_acme-challenge.owa.mcc.rsa.ru.owa.mcc.rsa.ru		Name Error - The domain name does not exist	1

15. DomainService - Entries

No DomainServiceEntries entries found

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=3b1e0d62-1143-452e-8213-99242aac52ca

Last Result: https://check-your-website.server-daten.de/?q=owa.mcc.rsa.ru - 2023-11-20 10:07:11

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

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

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