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

0 in Queue, 1 of max. 8 Checks (20:56:27)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A

 

Top config

 

Checked:
14.08.2019 11:28:50

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
piwik.baden-wuerttemberg.de
A
89.146.222.228
Frankfurt am Main/Hesse/Germany (DE) - INTERNET AG Global Network
Hostname: powered.by.inet.de.222.146.89.in-addr.arpa
yes
1
0

AAAA

yes


www.piwik.baden-wuerttemberg.de

Name Error
yes
1
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• 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 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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






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






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



Zone: de

de
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






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






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






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 43128, Flags 256






Public Key with Algorithm 8, KeyTag 47740, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 29.08.2019, 12:00:00 +, Signature-Inception: 08.08.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: baden-wuerttemberg.de

baden-wuerttemberg.de
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "hr2e09f63itjoasft5c6qs2ererv7nrv" between the hashed NSEC3-owner "hr2dga0brtsfivu8d3tnafjff0284iac" and the hashed NextOwner "hr2iogitm144nelui5tr8aku3239ivnd". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner hr2dga0brtsfivu8d3tnafjff0284iac.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 21.08.2019, 08:01:05 +, Signature-Inception: 14.08.2019, 08:01:05 +, KeyTag 43128, Signer-Name: de






0 DNSKEY RR found









Zone: piwik.baden-wuerttemberg.de

piwik.baden-wuerttemberg.de
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.piwik.baden-wuerttemberg.de

www.piwik.baden-wuerttemberg.de
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.piwik.baden-wuerttemberg.de
•  k1z01s003.kivbf.de

piwik.baden-wuerttemberg.de
•  k1z01s003.kivbf.de
194.59.36.5
Heilbronn/Baden-Württemberg Region/Germany (DE) - Kommunale Informationsverarbeitung Baden Franken		•
baden-wuerttemberg.de
•  k1z01s003.kivbf.de
•

•  k1z01s004.kivbf.de
•

•  ns.frei.net
•
de
•  a.nic.de / ns-2.de.de8.bind
•

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

•  l.de.net / ns-1.de.fr1.bind
•

•  n.de.net / s3.amx
•

•  s.de.net / ns-2.de.de9.bind
•

•  z.nic.de / ns-1.de.de8.bind
•

 

4. SOA-Entries


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


Domain:baden-wuerttemberg.de
Zone-Name:
Primary:k1z01s003.kivbf.de
Mail:hostmaster.kivbf.de
Serial:2019071901
Refresh:21600
Retry:7200
Expire:604800
TTL:86400
num Entries:3


Domain:piwik.baden-wuerttemberg.de
Zone-Name:
Primary:k1z01s003.kivbf.de
Mail:hostmaster.kivbf.de
Serial:2019071901
Refresh:21600
Retry:7200
Expire:604800
TTL:86400
num Entries:1


Domain:www.piwik.baden-wuerttemberg.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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://piwik.baden-wuerttemberg.de/
89.146.222.228
302
https://piwik.baden-wuerttemberg.de/

0.060
A
Date: Wed, 14 Aug 2019 09:29:07 GMT
Server: Apache/2.2.22 (Debian)
X-Matomo-Request-Id: 6f43a
X-Robots-Tag: noindex
Location: https://piwik.baden-wuerttemberg.de/
Vary: Accept-Encoding
Content-Length: 0
Connection: close
Content-Type: text/html

• https://piwik.baden-wuerttemberg.de/
89.146.222.228
200


3.420
A
Date: Wed, 14 Aug 2019 09:29:07 GMT
Server: Apache/2.2.22 (Debian)
Strict-Transport-Security: max-age=15768000
X-Matomo-Request-Id: 231f9
Set-Cookie: MATOMO_SESSID=td4ocmukk9ise4katibbj8hhn4; Path=/; Domain=piwik.baden-wuerttemberg.de; HttpOnly; Secure
Cache-Control: no-store, must-revalidate
X-Frame-Options: sameorigin
Referrer-Policy: same-origin
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

• http://piwik.baden-wuerttemberg.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
89.146.222.228
404


0.040
A
Not Found
Visible Content:
Date: Wed, 14 Aug 2019 09:29:11 GMT
Server: Apache/2.2.22 (Debian)
Vary: Accept-Encoding
Content-Length: 360
Connection: close
Content-Type: text/html; charset=iso-8859-1

 

7. Comments


1. General Results, most used to calculate the result

Aname "piwik.baden-wuerttemberg.de" is subdomain, 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
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: every cookie sent via https is marked as secure
AGood: every https has a Strict Transport Security Header
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://piwik.baden-wuerttemberg.de/ 89.146.222.228
302
https://piwik.baden-wuerttemberg.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

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: k1z01s003.kivbf.de: 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.

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
ADuration: 33184 milliseconds, 33.184 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
piwik.baden-wuerttemberg.de
89.146.222.228
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok
piwik.baden-wuerttemberg.de
89.146.222.228
443
ok
Tls12

DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
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
Chain - incomplete

1CN=*.baden-wuerttemberg.de


2CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US

 

9. Certificates

1.
1.
CN=*.baden-wuerttemberg.de
02.07.2018
29.03.2020
1879 days expired		*.baden-wuerttemberg.de, baden-wuerttemberg.de - 2 entries
1.
1.
CN=*.baden-wuerttemberg.de
02.07.2018

29.03.2020
1879 days expired


*.baden-wuerttemberg.de, baden-wuerttemberg.de - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0C1783B39F72365B06C5016CF9B3E454
Thumbprint:F632DDFF359BD7EAA7228025384071AC69F5D1F4
SHA256 / Certificate:y96H/wR7YsViPK7+iyK3fjIfU5pAh98hLwv68F6uwmQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):6b7d1ed93bf620c3e1f52d63d6d087a1e4b7f4869b722b95109d7b384631e723
SHA256 hex / Subject Public Key Information (SPKI):6b7d1ed93bf620c3e1f52d63d6d087a1e4b7f4869b722b95109d7b384631e723
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://status.rapidssl.com
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=*.baden-wuerttemberg.de
02.07.2018
29.03.2020
1879 days expired		*.baden-wuerttemberg.de, baden-wuerttemberg.de - 2 entries

2.
CN=*.baden-wuerttemberg.de
02.07.2018

29.03.2020
1879 days expired


*.baden-wuerttemberg.de, baden-wuerttemberg.de - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0C1783B39F72365B06C5016CF9B3E454
Thumbprint:F632DDFF359BD7EAA7228025384071AC69F5D1F4
SHA256 / Certificate:y96H/wR7YsViPK7+iyK3fjIfU5pAh98hLwv68F6uwmQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):6b7d1ed93bf620c3e1f52d63d6d087a1e4b7f4869b722b95109d7b384631e723
SHA256 hex / Subject Public Key Information (SPKI):6b7d1ed93bf620c3e1f52d63d6d087a1e4b7f4869b722b95109d7b384631e723
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://status.rapidssl.com
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)




3.
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
02.11.2017
02.11.2027
expires in 895 days

3.
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
02.11.2017

02.11.2027
expires in 895 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0B259422CED9812A15A04E99528A0EFA
Thumbprint:CBFE9EB43B3B37FE0DFBC4C2EB2D4E07D08BD8E8
SHA256 / Certificate:RCLpY+5TzVjMn4XNQL9f/sAJX98aFUU1ZhwcBrytxps=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):137b58730a3d0a2a804e62ada4c2d6e55fa9cc8abe6680e6a574a22655c6993a
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.com
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)




4.
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
02.11.2017
02.11.2027
expires in 895 days

4.
CN=RapidSSL TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
02.11.2017

02.11.2027
expires in 895 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0B259422CED9812A15A04E99528A0EFA
Thumbprint:CBFE9EB43B3B37FE0DFBC4C2EB2D4E07D08BD8E8
SHA256 / Certificate:RCLpY+5TzVjMn4XNQL9f/sAJX98aFUU1ZhwcBrytxps=
SHA256 hex / Cert (DANE * 0 1):4422e963ee53cd58cc9f85cd40bf5ffec0095fdf1a154535661c1c06bcadc69b
SHA256 hex / PublicKey (DANE * 1 1):137b58730a3d0a2a804e62ada4c2d6e55fa9cc8abe6680e6a574a22655c6993a
SHA256 hex / Subject Public Key Information (SPKI):137b58730a3d0a2a804e62ada4c2d6e55fa9cc8abe6680e6a574a22655c6993a
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
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)




5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
18.01.2024
10.11.2031
expires in 2364 days

5.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
18.01.2024

10.11.2031
expires in 2364 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0FE032AB844D033106C50C8E13C8B068
Thumbprint:8BF7F178A745A11BAC6AE5B586FC1838EADCB2CF
SHA256 / Certificate:edV7Fd+mXChw6v4Rtjd2WQnP6Te0nBXOfxlAMMqzla0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.digicert.cn
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013
15.01.2038
expires in 4622 days

6.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013

15.01.2038
expires in 4622 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:033AF1E6A711A9A0BB2864B11D09FAE5
Thumbprint:DF3C24F9BFD666761B268073FE06D1CC8D4F82A4
SHA256 / Certificate:yzzLt2Ax5eATj43TmiP53kf/w15DwRRM6ifUalqxy18=
SHA256 hex / Cert (DANE * 0 1):cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
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:





7.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006
10.11.2031
expires in 2364 days

7.
CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
10.11.2006

10.11.2031
expires in 2364 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:083BE056904246B1A1756AC95991C74A
Thumbprint:A8985D3A65E5E5C4B2D7D66D40C6DD2FB19C5436
SHA256 / Certificate:Q0ig6URMeMsmXgWNXolEtNhPlmK9Jtslf4k0pEPHAWE=
SHA256 hex / Cert (DANE * 0 1):4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
SHA256 hex / PublicKey (DANE * 1 1):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
SHA256 hex / Subject Public Key Information (SPKI):aff988906dde12955d9bebbf928fdcc31cce328d5b9384f21c8941ca26e20391
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)

Small Code Update - wait one minute

 

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

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

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
piwik.baden-wuerttemberg.de
0

no CAA entry found
1
0
baden-wuerttemberg.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
baden-wuerttemberg.de
v=spf1 a aaaa mx a:smtp.inet.de a:smtp2.inet.de ip6:2a01:130:8495:1002::1002 ~all
ok
1
0
piwik.baden-wuerttemberg.de

ok
1
0
_acme-challenge.piwik.baden-wuerttemberg.de

Name Error - The domain name does not exist
1
0
_acme-challenge.piwik.baden-wuerttemberg.de.baden-wuerttemberg.de

Name Error - The domain name does not exist
1
0
_acme-challenge.piwik.baden-wuerttemberg.de.piwik.baden-wuerttemberg.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 open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=57e32df1-6431-4f03-8cd4-608353b1e36f

 

Last Result: https://check-your-website.server-daten.de/?q=piwik.baden-wuerttemberg.de - 2019-08-14 11:28:50

 

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

 

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

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions