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



W

wrong Web-Response

Checked:
01.08.2020 11:15:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
wassermann.one
A
185.111.71.250
Lübeck/Schleswig-Holstein/Germany (DE) - Stadtwerke Luebeck GmbH
No Hostname found
yes
2
0

AAAA

yes


www.wassermann.one
CNAME
wassermann.one
yes
1
0

A
185.111.71.250
Lübeck/Schleswig-Holstein/Germany (DE) - Stadtwerke Luebeck GmbH
No Hostname found
yes


*.wassermann.one
A

yes



AAAA

yes



CNAME

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 46594, 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.2020, 00:00:00 +, Signature-Inception: 31.07.2020, 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: one
one
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 14131, DigestType 1 and Digest jAS0Q+52O4tnzfDbC7yDLiT1YO4=



DS with Algorithm 8, KeyTag 14131, DigestType 2 and Digest jRH/gaDpvMJxlpXL5NWFtHqjvebNKMWsbgK9kZypueA=



1 RRSIG RR to validate DS RR found



RRSIG-Owner one., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2020, 05:00:00 +, Signature-Inception: 01.08.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 29100, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner one., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 26.08.2020, 21:29:52 +, Signature-Inception: 27.07.2020, 20:31:00 +, KeyTag 14131, Signer-Name: one



RRSIG-Owner one., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 26.08.2020, 21:29:52 +, Signature-Inception: 27.07.2020, 20:31:00 +, KeyTag 29100, Signer-Name: one



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 14131, DigestType 1 and Digest "jAS0Q+52O4tnzfDbC7yDLiT1YO4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: wassermann.one
wassermann.one
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 "2939n9iu4p28t6039b6ccbcl270omc7b" between the hashed NSEC3-owner "291oa0hknjmb6tr4vol5550hromkkflo" and the hashed NextOwner "293uek29ti0b19v8ntvn39s9jf5l4mmj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 291oa0hknjmb6tr4vol5550hromkkflo.one., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 26.08.2020, 17:42:06 +, Signature-Inception: 27.07.2020, 17:33:54 +, KeyTag 29100, Signer-Name: one



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "f4cmn012br11ovo9u99g0pmvcn9bqfs7" as Owner. That's the Hash of "one" with the NextHashedOwnerName "f4gsfducs7vg0ni73msi3imvt535522j". So that domain name is the Closest Encloser of "wassermann.one". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner f4cmn012br11ovo9u99g0pmvcn9bqfs7.one., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 26.08.2020, 20:44:32 +, Signature-Inception: 27.07.2020, 20:08:36 +, KeyTag 29100, Signer-Name: one



0 DNSKEY RR found




Zone: www.wassermann.one
www.wassermann.one
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
wassermann.one
  docks04.rzone.de
81.169.146.14
Berlin/Land Berlin/Germany (DE) - Strato AG


 
2a01:238:20a:930:6653::d04
Berlin/Land Berlin/Germany (DE) - Strato AG


  shades02.rzone.de
85.214.0.232
Berlin/Land Berlin/Germany (DE) - Strato AG


 
2a01:238:20b:43:6653::502
Berlin/Land Berlin/Germany (DE) - Strato AG

one
  a.nic.one / dns3.frpar1


  b.nic.one / dns4.defra1


  c.nic.one / dns3.defra1


  d.nic.one / dns4.frpar1


4. SOA-Entries


Domain:one
Zone-Name:one
Primary:a.nic.one
Mail:support.ariservices.com
Serial:1596272738
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:4


Domain:wassermann.one
Zone-Name:wassermann.one
Primary:docks04.rzone.de
Mail:hostmaster.strato-rz.de
Serial:2020073101
Refresh:86400
Retry:7200
Expire:604800
TTL:300
num Entries:4


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://wassermann.one/
185.111.71.250 GZip used - 556 / 1033 - 46.18 %
200

Html is minified: 135.03 %
0.026
H
small visible content (num chars: 228)
Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started. Powered by Nginx Proxy Manager
Server: openresty
Date: Sat, 01 Aug 2020 09:15:49 GMT
Content-Type: text/html
Last-Modified: Fri, 10 Jul 2020 12:37:35 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"5f08610f-409"
Content-Encoding: gzip

• http://www.wassermann.one/
185.111.71.250 GZip used - 556 / 1033 - 46.18 %
200

Html is minified: 135.03 %
0.026
H
small visible content (num chars: 228)
Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started. Powered by Nginx Proxy Manager
Server: openresty
Date: Sat, 01 Aug 2020 09:15:50 GMT
Content-Type: text/html
Last-Modified: Fri, 10 Jul 2020 12:37:35 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"5f08610f-409"
Content-Encoding: gzip

• https://wassermann.one/
185.111.71.250
-8

2.184
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors

• https://www.wassermann.one/
185.111.71.250
-8

2.177
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors

• http://wassermann.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.111.71.250 GZip used - 111 / 150 - 26.00 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.29 %
0.030
A
Not Found
Visible Content: 404 Not Found openresty
Server: openresty
Date: Sat, 01 Aug 2020 09:15:55 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• http://www.wassermann.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.111.71.250 GZip used - 111 / 150 - 26.00 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.29 %
0.027
A
Not Found
Visible Content: 404 Not Found openresty
Server: openresty
Date: Sat, 01 Aug 2020 09:15:55 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://185.111.71.250/
185.111.71.250
-8

2.150
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors

7. Comments


1. General Results, most used to calculate the result

Aname "wassermann.one" is domain, public suffix is ".one", top-level-domain is ".one", top-level-domain-type is "generic", tld-manager is "One.com A/S", num .one-domains preloaded: 118 (complete: 128404)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: wassermann.one has only one ip address.
Warning: Only one ip address found: www.wassermann.one 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: wassermann.one has no ipv6 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: www.wassermann.one has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
AGood: 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.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://wassermann.one/ 185.111.71.250


Url with incomplete Content-Type - header - missing charset
http://www.wassermann.one/ 185.111.71.250


Url with incomplete Content-Type - header - missing charset
http://wassermann.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.111.71.250


Url with incomplete Content-Type - header - missing charset
http://www.wassermann.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.111.71.250


Url with incomplete Content-Type - header - missing charset
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Hfatal error: No https - result with http-status 200, no encryption
HFatal 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.
Nhttps://wassermann.one/ 185.111.71.250
-8

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.wassermann.one/ 185.111.71.250
-8

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://185.111.71.250/ 185.111.71.250
-8

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain wassermann.one, 1 ip addresses, 1 different http results.
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.wassermann.one, 1 ip addresses, 1 different http results.

2. DNS- and NameServer - Checks

AInfo:: 49 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 49 Queries complete, 49 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 24.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: docks04.rzone.de, shades02.rzone.de, 2 Name Servers included in Delegation: docks04.rzone.de, shades02.rzone.de, 2 Name Servers included in 1 Zone definitions: docks04.rzone.de, shades02.rzone.de, 1 Name Servers listed in SOA.Primary: docks04.rzone.de.
AGood: Only one SOA.Primary Name Server found.: docks04.rzone.de.
AGood: SOA.Primary Name Server included in the delegation set.: docks04.rzone.de.
AGood: Consistency 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. Ordered list of name servers: docks04.rzone.de, shades02.rzone.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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 Name Servers, 1 Top Level Domain: de
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: rzone.de
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 81., 85., 2 different subnets (first two Bytes): 81.169., 85.214., 2 different subnets (first three Bytes): 81.169.146., 85.214.0.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 1 different subnets (first two blocks): 2a01:0238:, 2 different subnets (first three blocks): 2a01:0238:020a:, 2a01:0238:020b:, 2 different subnets (first four blocks): 2a01:0238:020a:0930:, 2a01:0238:020b:0043:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: docks04.rzone.de
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: shades02.rzone.de
Nameserver doesn't pass all EDNS-Checks: docks04.rzone.de / 81.169.146.14: 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: docks04.rzone.de / 2a01:238:20a:930:6653::d04: 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: shades02.rzone.de / 85.214.0.232: 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: shades02.rzone.de / 2a01:238:20b:43:6653::502: 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: 49666 milliseconds, 49.666 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
wassermann.one
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
wassermann.one
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=localhost, OU=Dummy Certificate, O=Nginx Proxy Manager


www.wassermann.one
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

www.wassermann.one
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=localhost, OU=Dummy Certificate, O=Nginx Proxy Manager


185.111.71.250
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

185.111.71.250
185.111.71.250
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=localhost, OU=Dummy Certificate, O=Nginx Proxy Manager


9. Certificates

1.
1.
CN=localhost, OU=Dummy Certificate, O=Nginx Proxy Manager
31.07.2020
29.07.2030
expires in 3643 days

1.
1.
CN=localhost, OU=Dummy Certificate, O=Nginx Proxy Manager
31.07.2020

29.07.2030
expires in 3643 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:43D9F40DCECB632B90D34B275794B385E52CE182
Thumbprint:C7500A3E1375E353BE8FDFE5663B3DC255404537
SHA256 / Certificate:cgmGZI8JhtR+kzl0URixPeiJZzR5HZdQtdojQvB8Mww=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):0a42d739cd72b0b74b9ac432f23ac4eab377ab48bf63f533bbaa5d07c962d7c2
SHA256 hex / Subject Public Key Information (SPKI):c004765f1a49f5c37f0722690f6921f7c8669838009f42e887aebd4db687d727
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
1
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1813446744
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-31 13:20:40
2020-10-29 13:20:40
wassermann.one - 1 entries
duplicate nr. 1


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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3170372264
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-31 11:20:40
2020-10-29 12:20:40
wassermann.one
1 entries
duplicate nr. 1


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: docks04.rzone.de, shades02.rzone.de

QNr.DomainTypeNS used
1
de
NS
k.root-servers.net (2001:7fd::1)

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2
docks04.rzone.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-anyslv.ui-dns.de, ns1.rzone.de, ns2.rzone.de, ns4.rzone.de

Answer: ns1.rzone.de
193.141.3.6

Answer: ns2.rzone.de
81.169.144.234

Answer: ns4.rzone.de
192.166.192.4, 2a01:238:e100:192::4
3
shades02.rzone.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-anyslv.ui-dns.de, ns1.rzone.de, ns2.rzone.de, ns4.rzone.de

Answer: ns1.rzone.de
193.141.3.6

Answer: ns2.rzone.de
81.169.144.234

Answer: ns4.rzone.de
192.166.192.4, 2a01:238:e100:192::4
4
ns-anyslv.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
5
biz
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, e.gtld.biz, f.gtld.biz, k.gtld.biz
6
ns-de.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
7
com
NS
f.root-servers.net (2001:500:2f::f)

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-de.ui-dns.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
9
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
10
ns-de.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
11
ns-biz.ui-dns.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
12
ns-biz.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
13
ns-biz.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
14
ns-com.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
15
ns-com.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
16
ns-com.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
17
ns-org.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
18
ns-org.ui-dns.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
19
ns-org.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
20
ns-anyslv.ui-dns.de: 217.160.80.247
A
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
21
ns-anyslv.ui-dns.de: 2001:8d8:fe:53:616e:7973:6c76:310a
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
22
ns-de.ui-dns.biz: 217.160.81.193
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
23
ns-de.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c1:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
24
ns-de.ui-dns.com: 217.160.82.193
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
25
ns-de.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c1:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
26
ns-de.ui-dns.org: 217.160.83.193
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
27
ns-de.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c1:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
28
ns-biz.ui-dns.com: 217.160.82.195
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
29
ns-biz.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c3:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
30
ns-biz.ui-dns.de: 217.160.80.195
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
31
ns-biz.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c3:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
32
ns-biz.ui-dns.org: 217.160.83.195
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
33
ns-biz.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c3:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
34
ns-com.ui-dns.biz: 217.160.81.194
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
35
ns-com.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c2:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
36
ns-com.ui-dns.de: 217.160.80.194
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
37
ns-com.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c2:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
38
ns-com.ui-dns.org: 217.160.83.194
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
39
ns-com.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c2:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
40
ns-org.ui-dns.biz: 217.160.81.196
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
41
ns-org.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c4:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
42
ns-org.ui-dns.com: 217.160.82.196
A
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
43
ns-org.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c4:100
AAAA
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
44
ns-org.ui-dns.de: 217.160.80.196
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
45
ns-org.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c4:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
46
docks04.rzone.de: 81.169.146.14
A
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
47
docks04.rzone.de: 2a01:238:20a:930:6653::d04
AAAA
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
48
shades02.rzone.de: 85.214.0.232
A
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
49
shades02.rzone.de: 2a01:238:20b:43:6653::502
AAAA
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.wassermann.one



1
0
wassermann.one
0

no CAA entry found
1
0
one
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
wassermann.one

ok
1
0
www.wassermann.one


1
0
_acme-challenge.wassermann.one

missing entry or wrong length
1
0
_acme-challenge.www.wassermann.one

Name Error - The domain name does not exist
1
0
_acme-challenge.wassermann.one.wassermann.one

perhaps wrong
1
0
_acme-challenge.www.wassermann.one.wassermann.one

perhaps wrong
1
0
_acme-challenge.www.wassermann.one.www.wassermann.one

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=2e913f0f-f0ba-4057-93b2-ad95c51e506d


Last Result: https://check-your-website.server-daten.de/?q=wassermann.one - 2020-08-01 11:15:31


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

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