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


 

 

A

 

Top config

 

Checked:
18.01.2019 15:45:27

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
somlen.de
A
89.238.87.229
Hostname: blast.somlen.de
yes
1
0

A
89.238.87.229
Hostname: blast.somlen.de
yes
1
0

AAAA
2A00:1828:A019:0000:0000:0000:0103:0000

yes


www.somlen.de
CNAME
blast.somlen.de
yes
1
0

A
89.238.87.229
Hostname: blast.somlen.de
yes


blast.somlen.de
AAAA
2A00:1828:A019:0000:0000:0000:0103:0000

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2019, 00:00:00 +, Signature-Inception: 11.01.2019, 00:00:00 +, KeyTag 19164, Signer-Name: (root)






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2019, 00:00:00 +, Signature-Inception: 11.01.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






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






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






2 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 9253, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 07.02.2019, 12:00:00 +, Signature-Inception: 17.01.2019, 12:00:00 +, KeyTag 39227, Signer-Name: de






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






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



Zone: somlen.de

somlen.de
0 DS RR in the parent zone found






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 64191, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner somlen.de., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 31.01.2019, 04:29:08 +, Signature-Inception: 17.01.2019, 02:59:08 +, KeyTag 36677, Signer-Name: somlen.de






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






Error: DNSKEY 36677 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Zone: www.somlen.de

www.somlen.de
0 DS RR in the parent zone found






Validated: RRSIG-Owner www.somlen.de., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 31.01.2019, 04:29:08 +, Signature-Inception: 17.01.2019, 02:59:08 +, KeyTag 64191, Signer-Name: somlen.de



Zone: (root)

(root)
1 DS RR published






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2019, 00:00:00 +, Signature-Inception: 11.01.2019, 00:00:00 +, KeyTag 19164, Signer-Name: (root)






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2019, 00:00:00 +, Signature-Inception: 11.01.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






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






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






2 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 9253, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 07.02.2019, 12:00:00 +, Signature-Inception: 17.01.2019, 12:00:00 +, KeyTag 39227, Signer-Name: de






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






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



Zone: somlen.de

somlen.de
0 DS RR in the parent zone found






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 64191, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner somlen.de., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 31.01.2019, 04:29:08 +, Signature-Inception: 17.01.2019, 02:59:08 +, KeyTag 36677, Signer-Name: somlen.de






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






Error: DNSKEY 36677 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Zone: blast.somlen.de

blast.somlen.de
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
somlen.de
  ns.inwx.de


  ns1.somlen.de


  ns2.inwx.de


  ns2.somlen.de


  ns4.inwx.com


  ns5.inwx.net

de
  a.nic.de


  f.nic.de


  l.de.net


  n.de.net


  s.de.net


  z.nic.de


blast.somlen.de
  ns1.somlen.de

somlen.de
  ns.inwx.de


  ns1.somlen.de


  ns2.inwx.de


  ns2.somlen.de


  ns4.inwx.com


  ns5.inwx.net

de
  a.nic.de


  f.nic.de


  l.de.net


  n.de.net


  s.de.net


  z.nic.de

 

4. SOA-Entries

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://somlen.de/
89.238.87.229
301
https://somlen.de/

0.044
A
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:39 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://somlen.de/
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin

• http://www.somlen.de/
89.238.87.229
301
https://www.somlen.de/

0.047
A
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:39 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://www.somlen.de/
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin

• https://www.somlen.de/
89.238.87.229
301
https://somlen.de/

1.263
A
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:40 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://somlen.de/
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin
Strict-Transport-Security: max-age=15768000

• https://somlen.de/
89.238.87.229
200


1.333
A
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:39 GMT
Content-Type: text/html
Content-Length: 375
Last-Modified: Sun, 26 Feb 2017 12:47:57 GMT
Connection: close
ETag: "58b2ce7d-177"
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin
Strict-Transport-Security: max-age=15768000
Content-Security-Policy: default-src 'none'; style-src 'self'; img-src 'self'; font-src 'self'; media-src 'self'; form-action 'self'; frame-ancestors 'self'; base-uri 'self';
Accept-Ranges: bytes

• http://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
89.238.87.229
301
https://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.050
A
Visible Content:
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:41 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin

• http://www.somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
89.238.87.229
301
https://www.somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.043
A
Visible Content:
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:41 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://www.somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin

• https://www.somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

301
https://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

1.243
A
Visible Content:
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:43 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin
Strict-Transport-Security: max-age=15768000

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

404


1.233
A
Not Found
Visible Content:
Server: nginx/1.10.3
Date: Fri, 18 Jan 2019 14:45:41 GMT
Content-Type: text/html
Content-Length: 169
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "somlen.de" is domain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every https has a Strict Transport Security Header
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)
https://somlen.de/ 89.238.87.229


Url with incomplete Content-Type - header - missing charset
https://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
Ahttp://somlen.de/ 89.238.87.229
301
https://somlen.de/
Correct redirect http - https with the same domain name
Ahttp://www.somlen.de/ 89.238.87.229
301
https://www.somlen.de/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: no CAA is allowed to create wildcard certificates

4. 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: 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://somlen.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
1.233 seconds
Warning: 404 needs more then one second
ADuration: 17093 milliseconds, 17.093 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
somlen.de
89.238.87.229
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
supported
ok
somlen.de
89.238.87.229
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0


www.somlen.de
89.238.87.229
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
supported
ok

www.somlen.de
89.238.87.229
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0

 

9. Certificates

1.
1.
CN=somlen.de
22.12.2018
22.03.2019
2155 days expired
mta-sts.somlen.de, somlen.de, www.somlen.de - 3 entries
1.
1.
CN=somlen.de
22.12.2018

22.03.2019
2155 days expired


mta-sts.somlen.de, somlen.de, www.somlen.de - 3 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:04ABB678F4E39443D1D8C114B59D0FFE047D
Thumbprint:7C0D3470D6DAD949411136CAB03A1419451DA9B6
SHA256 / Certificate:WNJaoJJPKr7fE9+Dj53aNmWP/GG7nHNVgWG+Ooke7cU=
SHA256 hex / Cert (DANE * 0 1):58d25aa0924f2abedf13df838f9dda36658ffc61bb9c73558161be3a891eedc5
SHA256 hex / PublicKey (DANE * 1 1):fb3cf80ae3ec153a0f7df27b26b4f41e3431e0077bad8e4d3c9020d719a73142
SHA256 hex / Subject Public Key Information (SPKI):fb3cf80ae3ec153a0f7df27b26b4f41e3431e0077bad8e4d3c9020d719a73142
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1429 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1429 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1232 days expired


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

30.09.2021
1232 days expired




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):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:




 

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

 

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

 

11. Html-Content - Entries

No Html-Content informations found. The feature is new (startet 2019-01-22), so recheck this domain.

 

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:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
blast.somlen.de
0

no CAA entry found
1
0
www.somlen.de



1
0
somlen.de
9
issuewild
;
1
0

9
issuewild
;
1
0

5
issue
letsencrypt.org
1
0

5
issue
letsencrypt.org
1
0

5
iodef
mailto:hostmaster@somlen.de
1
0

5
iodef
mailto:hostmaster@somlen.de
1
0
de
0

no CAA entry found
1
0

0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
somlen.de
v=spf1 mx ?all
ok
1
0
www.somlen.de


1
0
blast.somlen.de

ok
1
0
_acme-challenge.somlen.de

missing entry or wrong length
1
0
_acme-challenge.www.somlen.de

missing entry or wrong length
1
0
_acme-challenge.blast.somlen.de

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.somlen.de.www.somlen.de

Name Error - The domain name does not exist
1
0
_acme-challenge.blast.somlen.de.blast.somlen.de

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

 

 

Permalink: https://check-your-website.server-daten.de/?i=d985dcb6-a4b9-4cc5-ac9a-8e7457beb5fb

 

Last Result: https://check-your-website.server-daten.de/?q=somlen.de - 2019-01-18 15:45:27

 

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

 

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