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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
13.03.2025 08:35:00

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
server-11071.prod.hosts.ooklaserver.net	CNAME	speedtest-kld.megafon.ru	yes	1	0
	A	178.176.143.167 Kaliningrad/Kaliningrad Oblast/Russia (RU) - MegaFon No Hostname found	yes
	AAAA	2a03:d000:24c8::11 Moscow/Russia (RU) - MegaFon	yes
www.server-11071.prod.hosts.ooklaserver.net		Name Error	yes	1	0
*.prod.hosts.ooklaserver.net	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.server-11071.prod.hosts.ooklaserver.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 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 26470, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.03.2025, 05:00:00 +, Signature-Inception: 13.03.2025, 04:00:00 +, KeyTag 26470, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 10024, Flags 256


	Public Key with Algorithm 13, KeyTag 37331, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.03.2025, 15:10:35 +, Signature-Inception: 03.03.2025, 15:05:35 +, KeyTag 37331, Signer-Name: net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 37331 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ooklaserver.net
ooklaserver.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 "nte0omu79kookm3nr82e0nkr2ihbh3ff" between the hashed NSEC3-owner "ntdug2j9rg1fbnh785obobo3pivru70d" and the hashed NextOwner "nte1a8fsodkv2pfh92fo8icp3k2aspn6". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ntdug2j9rg1fbnh785obobo3pivru70d.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.03.2025, 03:11:32 +, Signature-Inception: 12.03.2025, 02:01:32 +, KeyTag 10024, 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 "ooklaserver.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 20.03.2025, 03:09:44 +, Signature-Inception: 13.03.2025, 01:59:44 +, KeyTag 10024, Signer-Name: net


	0 DNSKEY RR found




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

Zone: prod.hosts.ooklaserver.net
prod.hosts.ooklaserver.net	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: server-11071.prod.hosts.ooklaserver.net
server-11071.prod.hosts.ooklaserver.net	0 DS RR in the parent zone found

Zone: www.server-11071.prod.hosts.ooklaserver.net
www.server-11071.prod.hosts.ooklaserver.net	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 26470, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.04.2025, 00:00:00 +, Signature-Inception: 12.03.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 18374, DigestType 2 and Digest gFjQwIjZs/fzAIDiuMmASUQwFyKizOnuZvasdP6y4gA=


	1 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 37783, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 30.03.2025, 00:00:00 +, Signature-Inception: 10.03.2025, 00:00:00 +, KeyTag 18374, Signer-Name: ru


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


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

Zone: megafon.ru
megafon.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 "3brilptlibab8rrcvlhthn1p3ujvfici" between the hashed NSEC3-owner "3bmo61jishfj53s4pd0p3d5ghuaqi6ka" and the hashed NextOwner "3bv1cibkqp54ftguuk4snu7kd49vb2ho". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 3bmo61jishfj53s4pd0p3d5ghuaqi6ka.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.04.2025, 23:51:44 +, Signature-Inception: 07.03.2025, 14:14:40 +, KeyTag 37783, 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 "megafon.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: 09.04.2025, 19:08:33 +, Signature-Inception: 07.03.2025, 14:14:40 +, KeyTag 37783, Signer-Name: ru


	0 DNSKEY RR found




Zone: speedtest-kld.megafon.ru
speedtest-kld.megafon.ru	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
www.server-11071.prod.hosts.ooklaserver.net	• ns-1211.awsdns-23.org
prod.hosts.ooklaserver.net	• ns-1211.awsdns-23.org / cc851708bdc30ddee9225cae719e428a -	205.251.196.187 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5304:bb00::1 Dallas/Texas/United States (US) - Amazon.com, Inc.	•
	• ns-1882.awsdns-43.co.uk / a31006b84d5742f1b4b3ad981da8bfe4 -	205.251.199.90 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5307:5a00::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
	• ns-363.awsdns-45.com / aed692db8bd81524313ec5f77138ef84 -	205.251.193.107 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5301:6b00::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
	• ns-861.awsdns-43.net / 566f9f91320de94cd839a2c0f2d9e7d6 -	205.251.195.93 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5303:5d00::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
hosts.ooklaserver.net	• ns-1780.awsdns-30.co.uk
ooklaserver.net	• ns-1187.awsdns-20.org / 4225795370e74c610957ac776e5ec9e2 -	205.251.196.163 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5304:a300::1 Dallas/Texas/United States (US) - Amazon.com, Inc.	•
	• ns-121.awsdns-15.com / 31eb623cc2f55f97ba6a3889a641711b -	205.251.192.121 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5300:7900::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
	• ns-1780.awsdns-30.co.uk / d110fe86dbd129e14e7d2e14e3e9303c -	205.251.198.244 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:f400::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
	• ns-519.awsdns-00.net / df5672f57e53322b89d3d80d264b7a2e -	205.251.194.7 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5302:700::1 Seattle/Washington/United States (US) - Amazon.com, Inc.	•
net	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

speedtest-kld.megafon.ru	• ns1.misp.ru	193.201.230.1 Moscow/Russia (RU) - PJSC MegaFon	•
	•	2a03:d000:4006:1:193:201:230:1 Moscow/Russia (RU) - MegaFon-Moscow	•
megafon.ru	• ns1.misp.ru	193.201.230.1 Moscow/Russia (RU) - PJSC MegaFon	•
	•	2a03:d000:4006:1:193:201:230:1 Moscow/Russia (RU) - MegaFon-Moscow	•
	• ns2.misp.ru	193.201.231.1 Moscow/Russia (RU) - PJSC MegaFon	•
	•	2a03:d000:4002:3:193:201:231:1 Moscow/Russia (RU) - MegaFon-Moscow	•
	• ns5.misp.ru	78.41.103.194 Samara/Samara Oblast/Russia (RU) - Povolzhie Branch of OJSC MegaFon	•
ru	• a.dns.ripn.net / tau.ripn.net		•
	• b.dns.ripn.net / std-tau-02.ripn.net		•
	• d.dns.ripn.net / tau-lax.ripn.net		•
	• e.dns.ripn.net / gamma-ekt.ripn.net		•
	• f.dns.ripn.net / tau-vlv.ripn.net		•

4. SOA-Entries

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

Domain:	ooklaserver.net
Zone-Name:	ooklaserver.net
Primary:	ns-1780.awsdns-30.co.uk
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	8

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

Domain:	prod.hosts.ooklaserver.net
Zone-Name:	prod.hosts.ooklaserver.net
Primary:	ns-1211.awsdns-23.org
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	8

Domain:	www.server-11071.prod.hosts.ooklaserver.net
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:	4063734
Refresh:	86400
Retry:	14400
Expire:	2592000
TTL:	3600
num Entries:	5

Domain:	megafon.ru
Zone-Name:	megafon.ru
Primary:	ns1.misp.ru
Mail:	nossc.megafon.ru
Serial:	2025031202
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	5

Domain:	speedtest-kld.megafon.ru
Zone-Name:	megafon.ru
Primary:	ns1.misp.ru
Mail:	nossc.megafon.ru
Serial:	2025031202
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	10800
num Entries:	2

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://server-11071.prod.hosts.ooklaserver.net/ 178.176.143.167	-14	10.027	T
Timeout - The operation has timed out.

• http://server-11071.prod.hosts.ooklaserver.net/ 2a03:d000:24c8::11	-14	10.016	T
Timeout - The operation has timed out.

• https://server-11071.prod.hosts.ooklaserver.net/ 178.176.143.167	-14	10.133	T
Timeout - The operation has timed out.

• https://server-11071.prod.hosts.ooklaserver.net/ 2a03:d000:24c8::11	-14	10.013	T
Timeout - The operation has timed out.

• http://server-11071.prod.hosts.ooklaserver.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.176.143.167	-14	10.023	T
Timeout - The operation has timed out.
Visible Content:

• http://server-11071.prod.hosts.ooklaserver.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:d000:24c8::11	-14	10.024	T
Timeout - The operation has timed out.
Visible Content:

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

• https://[2a03:d000:24c8:0000:0000:0000:0000:0011]/ 2a03:d000:24c8::11	-14	10.020	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "server-11071.prod.hosts.ooklaserver.net" is subdomain, 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: 9994 (complete: 263653)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: server-11071.prod.hosts.ooklaserver.net has 2 different ip addresses (authoritative).
A	Good: Ipv4 and Ipv6 addresses per domain name found: server-11071.prod.hosts.ooklaserver.net has 1 ipv4, 1 ipv6 addresses
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: b.gtld-servers.net: Timeout
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain server-11071.prod.hosts.ooklaserver.net, 2 ip addresses.
	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 server-11071.prod.hosts.ooklaserver.net, 2 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.server-11071.prod.hosts.ooklaserver.net
	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:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns-1211.awsdns-23.org, ns-1882.awsdns-43.co.uk, ns-363.awsdns-45.com, ns-861.awsdns-43.net, 4 Name Servers included in Delegation: ns-1211.awsdns-23.org, ns-1882.awsdns-43.co.uk, ns-363.awsdns-45.com, ns-861.awsdns-43.net, 4 Name Servers included in 1 Zone definitions: ns-1211.awsdns-23.org, ns-1882.awsdns-43.co.uk, ns-363.awsdns-45.com, ns-861.awsdns-43.net, 1 Name Servers listed in SOA.Primary: ns-1211.awsdns-23.org.
A	Good: Only one SOA.Primary Name Server found.: ns-1211.awsdns-23.org.
A	Good: SOA.Primary Name Server included in the delegation set.: ns-1211.awsdns-23.org.
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: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.193., 205.251.195., 205.251.196., 205.251.199.
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): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5303:, 2600:9000:5304:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5301:6b00:, 2600:9000:5303:5d00:, 2600:9000:5304:bb00:, 2600:9000:5307:5a00:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns-1211.awsdns-23.org: 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: ns-1780.awsdns-30.co.uk: 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.
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://server-11071.prod.hosts.ooklaserver.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.176.143.167	-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://server-11071.prod.hosts.ooklaserver.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:d000:24c8::11	-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: 267740 milliseconds, 267.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)

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

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
9241025965 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-01-17 06:17:44	2025-04-17 06:17:43	server-11071.prod.hosts.ooklaserver.net, speedtest-kld.megafon.ru.prod.hosts.ooklaserver.net - 2 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: ns-1211.awsdns-23.org, ns-1882.awsdns-43.co.uk, ns-363.awsdns-45.com, ns-861.awsdns-43.net

QNr.	Domain	Type	NS used
1	org	NS	b.root-servers.net (2001:500:200::b)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
2	ns-1211.awsdns-23.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: g-ns-1050.awsdns-23.org, g-ns-151.awsdns-23.org, g-ns-1623.awsdns-23.org, g-ns-729.awsdns-23.org
	Answer: g-ns-1050.awsdns-23.org 205.251.196.26, 2600:9000:5304:1a00::1
	Answer: g-ns-151.awsdns-23.org 205.251.192.151, 2600:9000:5300:9700::1
	Answer: g-ns-1623.awsdns-23.org 205.251.198.87, 2600:9000:5306:5700::1
	Answer: g-ns-729.awsdns-23.org 205.251.194.217, 2600:9000:5302:d900::1
3	uk	NS	c.root-servers.net (2001:500:2::c)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
4	ns-1882.awsdns-43.co.uk	NS	dns1.nic.uk (2a01:618:400::1)
	Answer: g-ns-1518.awsdns-43.co.uk, g-ns-1839.awsdns-43.co.uk, g-ns-363.awsdns-43.co.uk, g-ns-939.awsdns-43.co.uk
	Answer: g-ns-1518.awsdns-43.co.uk 205.251.197.238, 2600:9000:5305:ee00::1
	Answer: g-ns-1839.awsdns-43.co.uk 205.251.199.47, 2600:9000:5307:2f00::1
	Answer: g-ns-363.awsdns-43.co.uk 205.251.193.107, 2600:9000:5301:6b00::1
	Answer: g-ns-939.awsdns-43.co.uk 205.251.195.171, 2600:9000:5303:ab00::1
5	com	NS	k.root-servers.net (2001:7fd::1)
	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
6	ns-363.awsdns-45.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: g-ns-1197.awsdns-45.com, g-ns-1773.awsdns-45.com, g-ns-46.awsdns-45.com, g-ns-621.awsdns-45.com
	Answer: g-ns-1197.awsdns-45.com 205.251.196.173, 2600:9000:5304:ad00::1
	Answer: g-ns-1773.awsdns-45.com 205.251.198.237, 2600:9000:5306:ed00::1
	Answer: g-ns-46.awsdns-45.com 205.251.192.46, 2600:9000:5300:2e00::1
	Answer: g-ns-621.awsdns-45.com 205.251.194.109, 2600:9000:5302:6d00::1
7	net	NS	m.root-servers.net (2001:dc3::35)
	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
8	ns-861.awsdns-43.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: g-ns-1387.awsdns-43.net, g-ns-1963.awsdns-43.net, g-ns-492.awsdns-43.net, g-ns-813.awsdns-43.net
	Answer: g-ns-1387.awsdns-43.net 205.251.197.107, 2600:9000:5305:6b00::1
	Answer: g-ns-1963.awsdns-43.net 205.251.199.171, 2600:9000:5307:ab00::1
	Answer: g-ns-492.awsdns-43.net 205.251.193.236, 2600:9000:5301:ec00::1
	Answer: g-ns-813.awsdns-43.net 205.251.195.45, 2600:9000:5303:2d00::1
9	ns-1211.awsdns-23.org: 205.251.196.187	A	g-ns-1050.awsdns-23.org (2600:9000:5304:1a00::1)
10	ns-1211.awsdns-23.org: 2600:9000:5304:bb00::1	AAAA	g-ns-1050.awsdns-23.org (2600:9000:5304:1a00::1)
11	ns-1882.awsdns-43.co.uk: 205.251.199.90	A	g-ns-1518.awsdns-43.co.uk (2600:9000:5305:ee00::1)
12	ns-1882.awsdns-43.co.uk: 2600:9000:5307:5a00::1	AAAA	g-ns-1518.awsdns-43.co.uk (2600:9000:5305:ee00::1)
13	ns-363.awsdns-45.com: 205.251.193.107	A	g-ns-1197.awsdns-45.com (2600:9000:5304:ad00::1)
14	ns-363.awsdns-45.com: 2600:9000:5301:6b00::1	AAAA	g-ns-1197.awsdns-45.com (2600:9000:5304:ad00::1)
15	ns-861.awsdns-43.net: 205.251.195.93	A	g-ns-1387.awsdns-43.net (2600:9000:5305:6b00::1)
16	ns-861.awsdns-43.net: 2600:9000:5303:5d00::1	AAAA	g-ns-1387.awsdns-43.net (2600:9000:5305:6b00::1)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
server-11071.prod.hosts.ooklaserver.net			1
prod.hosts.ooklaserver.net	0	no CAA entry found	1
speedtest-kld.megafon.ru	0	no CAA entry found	1
ooklaserver.net	0	no CAA entry found	1
megafon.ru	0	no CAA entry found	1
net	0	no CAA entry found	1
ru	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
prod.hosts.ooklaserver.net	ok	1
server-11071.prod.hosts.ooklaserver.net		1
_acme-challenge.speedtest-kld.megafon.ru	Name Error - The domain name does not exist	1
_acme-challenge.server-11071.prod.hosts.ooklaserver.net	Name Error - The domain name does not exist	1
_acme-challenge.speedtest-kld.megafon.ru.speedtest-kld.megafon.ru	Name Error - The domain name does not exist	1
_acme-challenge.server-11071.prod.hosts.ooklaserver.net.prod.hosts.ooklaserver.net	Name Error - The domain name does not exist	1
_acme-challenge.server-11071.prod.hosts.ooklaserver.net.server-11071.prod.hosts.ooklaserver.net	Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
SPF	TXT	server-11071.prod.hosts.ooklaserver.net					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=2687b0a8-4a45-4a3d-aefd-ef1673668a38

Last Result: https://check-your-website.server-daten.de/?q=server-11071.prod.hosts.ooklaserver.net - 2025-03-13 08:35:00

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

<a href="https://check-your-website.server-daten.de/?q=server-11071.prod.hosts.ooklaserver.net" target="_blank">Check this Site: server-11071.prod.hosts.ooklaserver.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

QR-Code of this page - https://check-your-website.server-daten.de/?d=server-11071.prod.hosts.ooklaserver.net