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



B

Missing HSTS or Cookie-warnings

Checked:
13.01.2021 18:14:57


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
wotsy.octopol.io
A
35.242.217.68
Frankfurt/Hesse/Germany (DE) - Google LLC
Hostname: 68.217.242.35.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.wotsy.octopol.io

Name Error
yes
1
0
*.octopol.io
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.wotsy.octopol.io
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 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=



1 RRSIG RR to validate DS RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.01.2021, 17:00:00 +, Signature-Inception: 13.01.2021, 16:00:00 +, KeyTag 42351, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 52269, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 57355, Signer-Name: io



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



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

Zone: octopol.io
octopol.io
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 "r8j9ls8t2cphcgo44ijmf9625bf4afva" between the hashed NSEC3-owner "r8ijvj8rfbap41p81dl5sb6e9ek25dro" and the hashed NextOwner "r8lbqrba885jerbdohkq5ktk6lb9upmg". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner r8ijvj8rfbap41p81dl5sb6e9ek25dro.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 52269, Signer-Name: io



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u92tce82j4l1t382opcath2ulsjsm9qg" as Owner. That's the Hash of "io" with the NextHashedOwnerName "u931ddlvcqoe3b8vq9vt7rjok0dilu6v". So that domain name is the Closest Encloser of "octopol.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u92tce82j4l1t382opcath2ulsjsm9qg.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2021, 17:13:21 +, Signature-Inception: 13.01.2021, 16:13:21 +, KeyTag 52269, Signer-Name: io



0 DNSKEY RR found




Zone: wotsy.octopol.io
wotsy.octopol.io
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.wotsy.octopol.io
www.wotsy.octopol.io
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.wotsy.octopol.io
  ns77.domaincontrol.com

wotsy.octopol.io
  ns77.domaincontrol.com / p21
97.74.108.49
Scottsdale/Arizona/United States (US) - Host Europe GmbH


 
2603:5:21c4::31
New York/United States (US) - Host Europe GmbH

octopol.io
  ns77.domaincontrol.com / p21
97.74.108.49
Scottsdale/Arizona/United States (US) - Host Europe GmbH


 
2603:5:21c4::31
New York/United States (US) - Host Europe GmbH


  ns78.domaincontrol.com / p10
173.201.76.49
Scottsdale/Arizona/United States (US) - Host Europe GmbH


 
2603:5:22c4::31
New York/United States (US) - Host Europe GmbH

io
  a0.nic.io / app19.iad1.hosts.meta.redstone.afilias-nst.info-2020121101


  a2.nic.io / LHR3


  b0.nic.io / ns087a.app32.ams2.afilias-nst.info


  c0.nic.io / ns087b.app5.ams2.afilias-nst.info


4. SOA-Entries


Domain:io
Zone-Name:io
Primary:a0.nic.io
Mail:noc.afilias-nst.info
Serial:1497991253
Refresh:10800
Retry:3600
Expire:2764800
TTL:900
num Entries:4


Domain:octopol.io
Zone-Name:octopol.io
Primary:ns77.domaincontrol.com
Mail:dns.jomax.net
Serial:2021011301
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


Domain:wotsy.octopol.io
Zone-Name:octopol.io
Primary:ns77.domaincontrol.com
Mail:dns.jomax.net
Serial:2021011301
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:2


Domain:www.wotsy.octopol.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://wotsy.octopol.io, address used: https://wotsy.octopol.io/, Screenshot created 2021-01-13 18:16:24 +00:0

Mobil (412px x 732px)

314 milliseconds

Screenshot mobile - https://wotsy.octopol.io/
Mobil + Landscape (732px x 412px)

297 milliseconds

Screenshot mobile landscape - https://wotsy.octopol.io/
Screen (1280px x 1680px)

446 milliseconds

Screenshot Desktop - https://wotsy.octopol.io/

Mobile- and other Chrome-Checks

widthheight
visual Viewport412732
content Size412732

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://wotsy.octopol.io/
35.242.217.68
308
https://wotsy.octopol.io/
Html is minified: 108.92 %
0.057
A
Server: nginx/1.19.1
Date: Wed, 13 Jan 2021 17:15:56 GMT
Content-Type: text/html
Content-Length: 171
Connection: close
Location: https://wotsy.octopol.io/

• https://wotsy.octopol.io/
35.242.217.68
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
2.363
B
small visible content (num chars: 48)
Octopol.io - Wotsy_Sides_Prod - 06/01/2021 17:00
Server: nginx/1.19.1
Date: Wed, 13 Jan 2021 17:15:56 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 48
Connection: close
Strict-Transport-Security: max-age=15724800; includeSubDomains

• http://wotsy.octopol.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.242.217.68
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
308
https://wotsy.octopol.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.92 %
0.053
A
Visible Content: 308 Permanent Redirect nginx/1.19.1
Server: nginx/1.19.1
Date: Wed, 13 Jan 2021 17:15:59 GMT
Content-Type: text/html
Content-Length: 171
Connection: close
Location: https://wotsy.octopol.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://wotsy.octopol.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
2.387
A
NOT FOUND
Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> 404 Not Found Not Found The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Server: nginx/1.19.1
Date: Wed, 13 Jan 2021 17:16:03 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 232
Connection: close
Strict-Transport-Security: max-age=15724800; includeSubDomains

• https://35.242.217.68/
35.242.217.68
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
2.320
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 21)
default backend - 404
Server: nginx/1.19.1
Date: Wed, 13 Jan 2021 17:16:00 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 21
Connection: close
Strict-Transport-Security: max-age=15724800; includeSubDomains

7. Comments


1. General Results, most used to calculate the result

Aname "wotsy.octopol.io" is subdomain, public suffix is ".io", top-level-domain is ".io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry", num .io-domains preloaded: 1613 (complete: 142558)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: wotsy.octopol.io 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: wotsy.octopol.io 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: destination is https
Agood - only one version with Http-Status 200
Agood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
Agood: every https has a Strict Transport Security Header
Agood: HSTS has includeSubdomains - directive
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://wotsy.octopol.io/ 35.242.217.68
308
https://wotsy.octopol.io/
correct redirect http - https with the same domain name
Bwarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15724800 seconds = 182 days found
Mhttps://35.242.217.68/ 35.242.217.68
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://35.242.217.68/ 35.242.217.68
404

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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain wotsy.octopol.io, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 27 Queries complete, 25 with IPv6, 2 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns77.domaincontrol.com, ns78.domaincontrol.com, 2 Name Servers included in Delegation: ns77.domaincontrol.com, ns78.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns77.domaincontrol.com, ns78.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns77.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns77.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns77.domaincontrol.com.
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: ns77.domaincontrol.com, ns78.domaincontrol.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: 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: 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: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.76., 97.74.108.
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): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21c4:, 2603:0005:22c4:, 2 different subnets (first four blocks): 2603:0005:21c4:0000:, 2603:0005:22c4:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns77.domaincontrol.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.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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
https://wotsy.octopol.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.387 seconds
Warning: 404 needs more then one second
https://35.242.217.68/ 35.242.217.68
404
2.320 seconds
Warning: 404 needs more then one second
ADuration: 94010 milliseconds, 94.010 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
wotsy.octopol.io
35.242.217.68
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
wotsy.octopol.io
35.242.217.68
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=wotsy.octopol.io

2CN=R3, O=Let's Encrypt, C=US


wotsy.octopol.io
wotsy.octopol.io
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

wotsy.octopol.io
wotsy.octopol.io
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=wotsy.octopol.io

2CN=R3, O=Let's Encrypt, C=US


35.242.217.68
35.242.217.68
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok

35.242.217.68
35.242.217.68
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co


9. Certificates

1.
1.
CN=wotsy.octopol.io
21.12.2020
21.03.2021
expires in 57 days
wotsy.octopol.io - 1 entry
1.
1.
CN=wotsy.octopol.io
21.12.2020

21.03.2021
expires in 57 days
wotsy.octopol.io - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03ABD7A2A5D203FC2B4DB3117EF0661CD1C9
Thumbprint:07181CC5C4F9977BF2B4877B7F336946B796AA46
SHA256 / Certificate:Uzz+fIUvna7qViIGg+PrHMzDH4SThnYL9ArqOIWv31Q=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):701bd357d5c70b4aae40103edadcfe3c2d3e701594acb7949221ded1a8bd6bb0
SHA256 hex / Subject Public Key Information (SPKI):88c60791e743d173440ee9a213837d0f553f6c159b7b3b9882d8647bd3a5d676
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


2.
CN=R3, O=Let's Encrypt, C=US
07.10.2020
29.09.2021
expires in 249 days


2.
CN=R3, O=Let's Encrypt, C=US
07.10.2020

29.09.2021
expires in 249 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:400175048314A4C8218C84A90C16CDDF
Thumbprint:48504E974C0DAC5B5CD476C8202274B24C8C7172
SHA256 / Certificate:cwwb3NhfV85dwLunM+XxulqSWyp3HWQKJvekVCJNrTs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 250 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 250 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):29cc40db5e2de462a311cbbafaa1dc466960002335ecdf3317f2cd05c1d0bedf
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:


2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
17.10.2020
17.10.2021
expires in 267 days
ingress.local - 1 entry
2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
17.10.2020

17.10.2021
expires in 267 days
ingress.local - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:3E1FD6D0E499BD1DCA89269BC3180D80
Thumbprint:C29B33EC5BB349AB5BF9751726B0412EE6387A49
SHA256 / Certificate:HptW6dcGt29SAg+6Di/uSLnYDxisayMDaKFtsdrinKk=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3999ee0ab3ea6d31ff3b5b0cc0d39b7236b3aa1dbf5ccfa2040993c803d98097
SHA256 hex / Subject Public Key Information (SPKI):4dbcde5cd719559e9679630bac82238d9c128a727ebec5c243fb968f10856537
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

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=R3, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2155287246
leaf cert
CN=R3, O=Let's Encrypt, C=US
2020-12-21 14:37:58
2021-03-21 14:37:58
wotsy.octopol.io - 1 entries



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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3811895554
leaf cert
CN=R3, O=Let's Encrypt, C=US
2020-12-21 13:37:58
2021-03-21 13:37:58
wotsy.octopol.io
1 entries



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: ns77.domaincontrol.com, ns78.domaincontrol.com

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
ns77.domaincontrol.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns78.domaincontrol.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
4
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
5
a1-245.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
6
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
7
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
8
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
9
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
10
a4-67.akam.net: 72.246.46.67
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
11
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a4-67.akam.net
72.246.46.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
23
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
ns77.domaincontrol.com: 97.74.108.49
A
a1-245.akam.net (2600:1401:2::f5)
25
ns77.domaincontrol.com: 2603:5:21c4::31
AAAA
a1-245.akam.net (2600:1401:2::f5)
26
ns78.domaincontrol.com: 173.201.76.49
A
a1-245.akam.net (2600:1401:2::f5)
27
ns78.domaincontrol.com: 2603:5:22c4::31
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
wotsy.octopol.io
0

no CAA entry found
1
0
octopol.io
0

no CAA entry found
1
0
io
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
octopol.io
google-site-verification=4dypMt3HkeMtrOsPRgVSxuDxjGSkbcUQMpM32VOtK5I
ok
1
0
octopol.io
v=spf1 include:_spf.google.com ~all
ok
1
0
wotsy.octopol.io

ok
1
0
_acme-challenge.wotsy.octopol.io

Name Error - The domain name does not exist
1
0
_acme-challenge.wotsy.octopol.io.octopol.io

Name Error - The domain name does not exist
1
0
_acme-challenge.wotsy.octopol.io.wotsy.octopol.io

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=4702ca95-e2b5-4f7f-b428-f276d8fd88e0


Last Result: https://check-your-website.server-daten.de/?q=wotsy.octopol.io - 2021-01-13 18:14: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=wotsy.octopol.io" target="_blank">Check this Site: wotsy.octopol.io</a>