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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
03.12.2025 09:36:57

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
grafana.ynikitin.ru	CNAME	gw.ynikitin.ru	yes	1	0
	A	78.136.223.81 Moscow/Russia (RU) - JSC "ER-Telecom Holding" Moscow region No Hostname found	yes
www.grafana.ynikitin.ru		Name Error	yes	1	0
*.ynikitin.ru	A	Name Error	yes
	AAAA	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.grafana.ynikitin.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


	3 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2025, 00:00:00 +, Signature-Inception: 30.11.2025, 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 51575, DigestType 2 and Digest NM9zU1MGDZvWNH/4Hs+qwk7I8Rlx3IACScZKIbwGJ3U=


	2 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 3835, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 21.12.2025, 00:00:00 +, Signature-Inception: 01.12.2025, 00:00:00 +, KeyTag 51575, Signer-Name: ru


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


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

Zone: ynikitin.ru
ynikitin.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 "vnj33tqpm7i8sp8m98m4fe609hbgdei0" between the hashed NSEC3-owner "vnetgk27ep75ue1e9nvigbf04nvaatpg" and the hashed NextOwner "vnmquc7cub87c4vuit1mr01j446ljel1". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vnetgk27ep75ue1e9nvigbf04nvaatpg.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.12.2025, 01:07:56 +, Signature-Inception: 10.11.2025, 10:15:00 +, KeyTag 3835, 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 "j21lulr2unpa28sere28ovnjnj67qp7v". So that domain name is the Closest Encloser of "ynikitin.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: 20.12.2025, 08:16:01 +, Signature-Inception: 10.11.2025, 10:15:00 +, KeyTag 3835, Signer-Name: ru


	0 DNSKEY RR found




Zone: grafana.ynikitin.ru
grafana.ynikitin.ru	0 DS RR in the parent zone found

Zone: www.grafana.ynikitin.ru
www.grafana.ynikitin.ru	0 DS RR in the parent zone found

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 20326, Flags 257 (SEP = Secure Entry Point)


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


	Public Key with Algorithm 8, KeyTag 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2025, 00:00:00 +, Signature-Inception: 30.11.2025, 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 51575, DigestType 2 and Digest NM9zU1MGDZvWNH/4Hs+qwk7I8Rlx3IACScZKIbwGJ3U=


	2 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 3835, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 21.12.2025, 00:00:00 +, Signature-Inception: 01.12.2025, 00:00:00 +, KeyTag 51575, Signer-Name: ru


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


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

Zone: ynikitin.ru
ynikitin.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 "vnj33tqpm7i8sp8m98m4fe609hbgdei0" between the hashed NSEC3-owner "vnetgk27ep75ue1e9nvigbf04nvaatpg" and the hashed NextOwner "vnmquc7cub87c4vuit1mr01j446ljel1". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vnetgk27ep75ue1e9nvigbf04nvaatpg.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.12.2025, 01:07:56 +, Signature-Inception: 10.11.2025, 10:15:00 +, KeyTag 3835, 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 "j21lulr2unpa28sere28ovnjnj67qp7v". So that domain name is the Closest Encloser of "ynikitin.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: 20.12.2025, 08:16:01 +, Signature-Inception: 10.11.2025, 10:15:00 +, KeyTag 3835, Signer-Name: ru


	0 DNSKEY RR found




Zone: gw.ynikitin.ru
gw.ynikitin.ru	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
www.grafana.ynikitin.ru	• ns1.reg.ru
ynikitin.ru	• ns1.reg.ru / ns-02-dc2.int.reg.ru	176.99.13.11 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.13 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.15 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.17 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	194.58.117.11 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.13 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.15 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.17 Moscow/Russia (RU) - Reg.Ru	•
	•	2a00:f940:9::1:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	2a00:f940:9::2:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	• ns2.reg.ru / ns-02-dc2.int.reg.ru	176.99.13.12 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.14 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.16 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.18 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	194.58.117.12 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.14 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.16 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.18 Moscow/Russia (RU) - Reg.Ru	•
	•	2a00:f940:9::1:2 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	2a00:f940:9::2:2 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
ru	• a.dns.ripn.net / tau.ripn.net		•
	• b.dns.ripn.net / m9p-tau-12.ripn.net
	• d.dns.ripn.net / nsk3-tau-01.ripn.net		•
	• e.dns.ripn.net / gamma-fra.ripn.net		•
	• f.dns.ripn.net / nyk-tau-01.ripn.net		•

gw.ynikitin.ru	• ns1.reg.ru / ns-02-dc2.int.reg.ru	176.99.13.11 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.13 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.15 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.17 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	194.58.117.11 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.13 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.15 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.17 Moscow/Russia (RU) - Reg.Ru	•
	•	2a00:f940:9::1:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	2a00:f940:9::2:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
ynikitin.ru	• ns1.reg.ru / ns-02-dc2.int.reg.ru	176.99.13.11 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.13 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.15 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.17 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	194.58.117.11 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.13 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.15 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.17 Moscow/Russia (RU) - Reg.Ru	•
	T	2a00:f940:9::1:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	2a00:f940:9::2:1 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	• ns2.reg.ru / ns-02-dc2.int.reg.ru	176.99.13.12 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.14 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.16 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	176.99.13.18 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	194.58.117.12 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.14 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.16 Moscow/Russia (RU) - Reg.Ru	•
	•	194.58.117.18 Moscow/Russia (RU) - Reg.Ru	•
	•	2a00:f940:9::1:2 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
	•	2a00:f940:9::2:2 Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd	•
ru	• a.dns.ripn.net / gamma.ripn.net		•
	• b.dns.ripn.net / m9p-tau-11.ripn.net
	• d.dns.ripn.net / nsk3-tau-03.ripn.net		•
	• e.dns.ripn.net / gamma-fra.ripn.net		•
	• f.dns.ripn.net / nyk-tau-01.ripn.net		•

4. SOA-Entries

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

Domain:	ynikitin.ru
Zone-Name:	ynikitin.ru
Primary:	ns1.reg.ru
Mail:	hostmaster.ns1.reg.ru
Serial:	1764749457
Refresh:	14400
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	20

Domain:	www.grafana.ynikitin.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1


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

Domain:	ynikitin.ru
Zone-Name:	ynikitin.ru
Primary:	ns1.reg.ru
Mail:	hostmaster.ns1.reg.ru
Serial:	1764749457
Refresh:	14400
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	20

Domain:	gw.ynikitin.ru
Zone-Name:	ynikitin.ru
Primary:	ns1.reg.ru
Mail:	hostmaster.ns1.reg.ru
Serial:	1764749457
Refresh:	14400
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	10

5. Screenshots

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

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://grafana.ynikitin.ru/ 78.136.223.81 gzip used - 397 / 615 - 35.45 %	200	Html is minified: 133.12 %	0.084	H
Server: nginx/1.24.0,(Ubuntu)
Date: Wed, 03 Dec 2025 08:40:18 GMT
Transfer-Encoding: chunked
Connection: keep-alive
ETag: W/"6434bbbe-267"
Content-Type: text/html
Last-Modified: Tue, 11 Apr 2023 01:45:34 GMT
Content-Encoding: gzip
Content-Length: 397

• https://grafana.ynikitin.ru/ 78.136.223.81	-14		10.024	T
Timeout - The operation has timed out.

• http://grafana.ynikitin.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 78.136.223.81 gzip used - 123 / 162 - 24.07 % Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 109.46 % Other inline scripts (∑/total): 0/0	0.050	A
Not Found
Visible Content:
Server: nginx/1.24.0,(Ubuntu)
Date: Wed, 03 Dec 2025 08:40:28 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/html
Content-Encoding: gzip
Content-Length: 123

• https://78.136.223.81/ 78.136.223.81	-14		10.023	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "grafana.ynikitin.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: 3331 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: grafana.ynikitin.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: grafana.ynikitin.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
A	Good - only one version with Http-Status 200
A	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
	http://grafana.ynikitin.ru/ 78.136.223.81	Url with incomplete Content-Type - header - missing charset
	http://grafana.ynikitin.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 78.136.223.81	Url with incomplete Content-Type - header - missing charset
H	Fatal error: No https - result with http-status 200, no encryption
H	Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
X	Fatal error: Nameserver doesn't support TCP connection: b.dns.ripn.net: 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 grafana.ynikitin.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.grafana.ynikitin.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:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: 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.reg.ru (176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 2a00:f940:9::1:1, 2a00:f940:9::2:1), ns2.reg.ru (176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 2a00:f940:9::1:2, 2a00:f940:9::2:2)
A	Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns1.reg.ru, ns2.reg.ru, 2 Name Servers included in Delegation: ns1.reg.ru, ns2.reg.ru, 2 Name Servers included in 1 Zone definitions: ns1.reg.ru, ns2.reg.ru, 1 Name Servers listed in SOA.Primary: ns1.reg.ru.
A	Good: Only one SOA.Primary Name Server found.: ns1.reg.ru.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.reg.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	Info: Ipv4-Subnet-list: 16 Name Servers, 2 different subnets (first Byte): 176., 194., 2 different subnets (first two Bytes): 176.99., 194.58., 2 different subnets (first three Bytes): 176.99.13., 194.58.117.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2a00:, 1 different subnets (first two blocks): 2a00:f940:, 1 different subnets (first three blocks): 2a00:f940:0009:, 1 different subnets (first four blocks): 2a00:f940:0009:0000:
	Fatal: All Name Server IPv6 addresses from the same subnet.
A	Good: Nameserver supports TCP connections: 40 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 40 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 40 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.reg.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: ns1.reg.ru / 2a00:f940:9::2:1: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns-01-dc1.int.reg.ru). COOKIE: ok. 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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 233640 milliseconds, 233.640 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)

Issuer				last 7 days	active	num Certs
CN=E8, O=Let's Encrypt, C=US				1	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12951225677 leaf cert	CN=E8, O=Let's Encrypt, C=US	2025-12-03 05:44:09	2026-03-03 05:44:08	grafana.ynikitin.ru - 1 entries

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months 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. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.reg.ru, ns2.reg.ru

QNr.	Domain	Type	NS used
1	ru	NS	a.root-servers.net (2001:503:ba3e::2:30)
	Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
2	ns1.reg.ru: 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 2a00:f940:9::1:1, 2a00:f940:9::2:1	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns2.reg.ru 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 2a00:f940:9::1:2, 2a00:f940:9::2:2

14. CAA - Entries

Domainname	flag	Value	∑ Queries
grafana.ynikitin.ru			1
gw.ynikitin.ru	0	no CAA entry found	1
ynikitin.ru	0	no CAA entry found	1
	0	no CAA entry found	1
ru	0	no CAA entry found	1
	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
ynikitin.ru	v=spf1 a mx -all	ok	1
grafana.ynikitin.ru			1
_acme-challenge.gw.ynikitin.ru		Name Error - The domain name does not exist	1
_acme-challenge.grafana.ynikitin.ru		Name Error - The domain name does not exist	1
_acme-challenge.gw.ynikitin.ru.gw.ynikitin.ru		Name Error - The domain name does not exist	1
_acme-challenge.grafana.ynikitin.ru.ynikitin.ru		Name Error - The domain name does not exist	1
_acme-challenge.grafana.ynikitin.ru.grafana.ynikitin.ru		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
SPF	TXT	grafana.ynikitin.ru					32768	TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=52b865dd-93e1-4190-9b31-e3db2c965f54

Last Result: https://check-your-website.server-daten.de/?q=grafana.ynikitin.ru - 2025-12-03 09:36:57

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

<a href="https://check-your-website.server-daten.de/?q=grafana.ynikitin.ru" target="_blank">Check this Site: grafana.ynikitin.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

QR-Code of this page - https://check-your-website.server-daten.de/?d=grafana.ynikitin.ru