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



V

Connect failure - perhaps firewall

Checked:
05.08.2022 18:50:12


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
kai.labspot.dev
A
203.129.28.106
Sydney/New South Wales/Australia (AU) - Aussie Broadband
Hostname: 203-129-28-106.cust.aussiebb.net
yes
1
0

AAAA

yes


www.kai.labspot.dev

Name Error
yes
1
0
*.labspot.dev
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.kai.labspot.dev
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 20826, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=



1 RRSIG RR to validate DS RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 05:00:00 +, Signature-Inception: 05.08.2022, 04:00:00 +, KeyTag 20826, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 26730, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 60074, Signer-Name: dev



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



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

Zone: labspot.dev
labspot.dev
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 "rsc3a5uq67heknehnf91pn36pbtbe39g" between the hashed NSEC3-owner "rsc3a5uq67heknehnf91pn36pbtbe39g" and the hashed NextOwner "rsc5it4gj1lijdtuu5aevrkhi0d7n27r". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner rsc3a5uq67heknehnf91pn36pbtbe39g.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 23.08.2022, 20:54:38 +, Signature-Inception: 01.08.2022, 20:54:38 +, KeyTag 26730, Signer-Name: dev



0 DNSKEY RR found




Zone: kai.labspot.dev
kai.labspot.dev
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.kai.labspot.dev
www.kai.labspot.dev
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.kai.labspot.dev
  ns1.onlydomains.com

kai.labspot.dev
  ns1.onlydomains.com / de-01.instradns.com
75.2.6.34
Seattle/Washington/United States (US) - Amazon.com, Inc.

labspot.dev
  ns1.onlydomains.com / de-01.instradns.com
75.2.6.34
Seattle/Washington/United States (US) - Amazon.com, Inc.


  ns2.onlydomains.com / de-01.instradns.com
75.2.85.37
Seattle/Washington/United States (US) - Amazon.com, Inc.


  ns3.onlydomains.com / de-01.instradns.com
99.83.188.20
Seattle/Washington/United States (US) - Amazon.com, Inc.

dev
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com


4. SOA-Entries


Domain:dev
Zone-Name:dev
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:labspot.dev
Zone-Name:labspot.dev
Primary:ns1.onlydomains.com
Mail:root.onlydomains.com
Serial:2021022801
Refresh:28800
Retry:7200
Expire:604800
TTL:86400
num Entries:3


Domain:kai.labspot.dev
Zone-Name:labspot.dev
Primary:ns1.onlydomains.com
Mail:root.onlydomains.com
Serial:2021022801
Refresh:28800
Retry:7200
Expire:604800
TTL:86400
num Entries:1


Domain:www.kai.labspot.dev
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

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

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://kai.labspot.dev/
203.129.28.106
404

Html is minified: 100.00 %
0.557
M
Not Found
date: Wed, 03 Aug 2022 16:50:44 GMT
server: uvicorn
content-length: 22
content-type: application/json
Connection: close

• https://kai.labspot.dev/
203.129.28.106
-2

1.817
V
ConnectFailure - Unable to connect to the remote server

• http://kai.labspot.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
203.129.28.106
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.554
A
Not Found
Visible Content: {"detail":"Not Found"}
date: Wed, 03 Aug 2022 16:50:46 GMT
server: uvicorn
content-length: 22
content-type: application/json
Connection: close

• https://203.129.28.106/
203.129.28.106
-2

1.816
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "kai.labspot.dev" is subdomain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 12 (complete: 175327)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: kai.labspot.dev 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: kai.labspot.dev has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: No cookie sent via http.
AExcellent: Main Domain is in the Google-Preload-List
AExcellent: Main Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: 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://kai.labspot.dev/ 203.129.28.106


Url with incomplete Content-Type - header - missing charset
http://kai.labspot.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 203.129.28.106


Url with incomplete Content-Type - header - missing charset
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption
Mhttp://kai.labspot.dev/ 203.129.28.106
404

Misconfiguration - main pages should never send http status 400 - 499
Vhttps://kai.labspot.dev/ 203.129.28.106
-2

connect failure - perhaps firewall
Vhttps://203.129.28.106/ 203.129.28.106
-2

connect failure - perhaps firewall
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 kai.labspot.dev, 1 ip addresses.

2. 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.onlydomains.com (75.2.6.34), ns2.onlydomains.com (75.2.85.37), ns3.onlydomains.com (99.83.188.20)
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.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, 3 Name Servers included in Delegation: ns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com, 0 Name Servers included in 1 Zone definitions: , 1 Name Servers listed in SOA.Primary: ns1.onlydomains.com.
AGood: Only one SOA.Primary Name Server found.: ns1.onlydomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.onlydomains.com.
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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 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.: 3 Name Servers, 1 Top Level Domain: com
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: onlydomains.com
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 75., 99., 2 different subnets (first two Bytes): 75.2., 99.83., 3 different subnets (first three Bytes): 75.2.6., 75.2.85., 99.83.188.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: 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: ns1.onlydomains.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

AGood: 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.
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: 49797 milliseconds, 49.797 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

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

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.onlydomains.com: 75.2.6.34
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.onlydomains.com
75.2.85.37

Answer: ns3.onlydomains.com
99.83.188.20


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
kai.labspot.dev
0

no CAA entry found
1
0
labspot.dev



1
0
dev
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
labspot.dev


1
0
kai.labspot.dev

ok
1
0
_acme-challenge.kai.labspot.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.kai.labspot.dev.labspot.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.kai.labspot.dev.kai.labspot.dev

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (alpha - see server-daten.de)

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks (OpenRelayCheck is alpha) (Some changes - now checks domain + ip address, results older 2022-07-31 15:00 may be wrong / invisible)

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



Permalink: https://check-your-website.server-daten.de/?i=b5136e87-dab1-4888-8f3b-2b101e7b615e


Last Result: https://check-your-website.server-daten.de/?q=kai.labspot.dev - 2022-08-05 18:50:12


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

<a href="https://check-your-website.server-daten.de/?q=kai.labspot.dev" target="_blank">Check this Site: kai.labspot.dev</a>