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


 

 

T

 

Timeout

 

Checked:
18.09.2023 21:45:41

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
domiflix.spider300x.de
CNAME
spider300x.de
yes
1
0

A
95.91.239.109
Munich/Bavaria/Germany (DE) - Vodafone Kabel Deutschland
Hostname: ip5f5bef6d.dynamic.kabel-deutschland.de
yes



AAAA
2a02:810d:443f:d67c:a44e:8051:27f:1e94
Munich/Bavaria/Germany (DE) - Vodafone Kabel Deutschland

yes


www.domiflix.spider300x.de

Name Error
yes
1
0
*.spider300x.de
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.domiflix.spider300x.de
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 11019, Flags 256






Public Key with Algorithm 8, KeyTag 20326, 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: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.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: de

de
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 26755, DigestType 2 and Digest 80E1eAmllUMRzLgq3hFMbB1ySnXAOVE3qjl4A1Ql540=






1 RRSIG RR to validate DS RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 05:00:00 +, Signature-Inception: 18.09.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 44886, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.09.2023, 23:42:55 +, Signature-Inception: 15.09.2023, 22:12:55 +, KeyTag 26755, Signer-Name: de






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






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



Zone: spider300x.de

spider300x.de
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 "si75eua0sua6hggbpl6m94g64n10vnjt" between the hashed NSEC3-owner "si7599ku2jel5b077t7v6pevrjo62oit" and the hashed NextOwner "si75jlom02449c57h4jb1mt9b9orp7kf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner si7599ku2jel5b077t7v6pevrjo62oit.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 02.10.2023, 00:37:54 +, Signature-Inception: 17.09.2023, 23:07:54 +, KeyTag 44886, Signer-Name: de






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tjlb7qbojvmlf1s6gdriru7vsms1lg16" as Owner. That's the Hash of "de" with the NextHashedOwnerName "tjlf6jn42vl7a95rc3u0k1aoglkqj53o". So that domain name is the Closest Encloser of "spider300x.de". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tjlb7qbojvmlf1s6gdriru7vsms1lg16.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 02.10.2023, 02:36:46 +, Signature-Inception: 18.09.2023, 01:06:46 +, KeyTag 44886, Signer-Name: de






0 DNSKEY RR found









Zone: domiflix.spider300x.de

domiflix.spider300x.de
0 DS RR in the parent zone found



Zone: www.domiflix.spider300x.de

www.domiflix.spider300x.de
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
spider300x.de
  ns1.hosting.de / dns-aac
134.0.30.178
Frankfurt am Main/Hesse/Germany (DE) - Hosting.de GmbH


 
2a03:2900:3:1::2
Aachen/North Rhine-Westphalia/Germany (DE) - Hosting.de GmbH


  ns2.hosting.de / dnsdist-ams
194.50.113.2
Aachen/North Rhine-Westphalia/Germany (DE) - Hosting.de GmbH


 
2001:4d8f:2::2
Aachen/North Rhine-Westphalia/Germany (DE) - Hosting.de GmbH


  ns3.hosting.de / dns-ffm
194.126.196.2
Frankfurt am Main/Hesse/Germany (DE) - IP- Accelerated IT Services GmbH


 
2a03:2902:3:1::2
Aachen/North Rhine-Westphalia/Germany (DE) - IP- Accelerated IT Services GmbH

de
  a.nic.de / ns-1.de.de8.bind


  f.nic.de / ns-2.de.de1


  l.de.net / ns-2.de.fr1


  n.de.net / s3.cmx


  s.de.net / ns-3.de.de9


  z.nic.de / ns-2.de.de2.bind

 

4. SOA-Entries


Domain:de
Zone-Name:de
Primary:f.nic.de
Mail:dns-operations.denic.de
Serial:1695066235
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:spider300x.de
Zone-Name:spider300x.de
Primary:ns1.hosting.de
Mail:hostmaster.spider300x.de
Serial:2023082901
Refresh:86400
Retry:7200
Expire:3600000
TTL:900
num Entries:6


5. Screenshots

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

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://domiflix.spider300x.de/
95.91.239.109
-14


10.040
T
Timeout - The operation has timed out

• http://domiflix.spider300x.de/
2a02:810d:443f:d67c:a44e:8051:27f:1e94
-14


10.043
T
Timeout - The operation has timed out

• https://domiflix.spider300x.de/
95.91.239.109
-14


10.050
T
Timeout - The operation has timed out

• https://domiflix.spider300x.de/
2a02:810d:443f:d67c:a44e:8051:27f:1e94
-14


10.030
T
Timeout - The operation has timed out

• http://domiflix.spider300x.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
95.91.239.109
-14


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

• http://domiflix.spider300x.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a02:810d:443f:d67c:a44e:8051:27f:1e94
-14


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

• https://95.91.239.109/
95.91.239.109
-14


10.040
T
Timeout - The operation has timed out

• https://[2a02:810d:443f:d67c:a44e:8051:027f:1e94]/
2a02:810d:443f:d67c:a44e:8051:27f:1e94
-14


10.040
T
Timeout - The operation has timed out

 

7. Comments


1. General Results, most used to calculate the result

Aname "domiflix.spider300x.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9157 (complete: 231048)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: domiflix.spider300x.de has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: domiflix.spider300x.de has 1 ipv4, 1 ipv6 addresses
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.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain domiflix.spider300x.de, 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 domiflix.spider300x.de, 2 ip addresses.
BNo _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.domiflix.spider300x.de

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 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.hosting.de (134.0.30.178, 2a03:2900:3:1::2), ns2.hosting.de (194.50.113.2, 2001:4d8f:2::2), ns3.hosting.de (194.126.196.2, 2a03:2902:3:1::2)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 3 Name Servers included in Delegation: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 3 Name Servers included in 1 Zone definitions: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 1 Name Servers listed in SOA.Primary: ns1.hosting.de.
AGood: Only one SOA.Primary Name Server found.: ns1.hosting.de.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.hosting.de.
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: 3 Name Servers, 2 different subnets (first Byte): 134., 194., 3 different subnets (first two Bytes): 134.0., 194.126., 194.50., 3 different subnets (first three Bytes): 134.0.30., 194.126.196., 194.50.113.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2a03:, 3 different subnets (first two blocks): 2001:4d8f:, 2a03:2900:, 2a03:2902:, 3 different subnets (first three blocks): 2001:4d8f:0002:, 2a03:2900:0003:, 2a03:2902:0003:, 3 different subnets (first four blocks): 2001:4d8f:0002:0000:, 2a03:2900:0003:0001:, 2a03:2902:0003:0001:
AGood: Name Server IPv6 addresses from different subnets 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
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
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.

4. Content- and Performance-critical Checks

http://domiflix.spider300x.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 95.91.239.109
-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://domiflix.spider300x.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a02:810d:443f:d67c:a44e:8051:27f:1e94
-14

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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5458426684
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-06-30 16:36:39
2023-09-28 16:36:38
domiflix.spider300x.de - 1 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9807583854
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-06-30 14:36:39
2023-09-28 14:36:38
domiflix.spider300x.de
1 entries


 

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/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de

 

QNr.DomainTypeNS used
1
de
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2
ns1.hosting.de: 134.0.30.178, 2a03:2900:3:1::2
NS
a.nic.de (2001:678:2::53)

Answer: ns3.hosting.de
194.126.196.2, 2a03:2902:3:1::2

Answer: ns2.hosting.de
194.50.113.2, 2001:4d8f:2::2

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
domiflix.spider300x.de



1
0
spider300x.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
spider300x.de

ok
1
0
domiflix.spider300x.de


1
0
_acme-challenge.domiflix.spider300x.de

Name Error - The domain name does not exist
1
0
_acme-challenge.domiflix.spider300x.de.spider300x.de

Name Error - The domain name does not exist
1
0
_acme-challenge.domiflix.spider300x.de.domiflix.spider300x.de

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

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=98310998-f35b-4e68-b4a4-99e935bf35ca

 

Last Result: https://check-your-website.server-daten.de/?q=domiflix.spider300x.de - 2023-09-18 21:45:41

 

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

 

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