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

0 in Queue, 0 of max. 8 Checks (18:15:09)
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:
16.08.2019 12:22:41

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tinminnow.me
A
140.82.59.163
Haarlem/North Holland/Netherlands (NL) - Choopa
Hostname: 140.82.59.163.vultr.com
yes
1
0

AAAA
2a05:f480:1400:674:5400:2ff:fe38:db91
New London/Connecticut/United States (US) - Choopa, LLC

yes


www.tinminnow.me

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: me

me
2 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.08.2019, 05:00:00 +, Signature-Inception: 16.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






4 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 2569, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 7, KeyTag 41612, Flags 256






Public Key with Algorithm 7, KeyTag 44630, Flags 256






Public Key with Algorithm 7, KeyTag 53233, Flags 257 (SEP = Secure Entry Point)






3 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2019, 15:24:31 +, Signature-Inception: 09.08.2019, 14:24:31 +, KeyTag 2569, Signer-Name: me






RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2019, 15:24:31 +, Signature-Inception: 09.08.2019, 14:24:31 +, KeyTag 44630, Signer-Name: me






RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2019, 15:24:31 +, Signature-Inception: 09.08.2019, 14:24:31 +, KeyTag 53233, Signer-Name: me






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 2569 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 44630 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 53233 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest "CboetNIEAmIIgf2YSJlEF4ANsmo=" 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 7, KeyTag 2569, DigestType 2 and Digest "lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: tinminnow.me

tinminnow.me
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 "ugr553l5t88pef308ojvqj4np9fqbubh" between the hashed NSEC3-owner "ugqp21lbm2hvbjkvd4247ntfn9ar9rvl" and the hashed NextOwner "ugrr76cu6no65oc1ep5n93gdug9ol8tj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ugqp21lbm2hvbjkvd4247ntfn9ar9rvl.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 30.08.2019, 15:24:31 +, Signature-Inception: 09.08.2019, 14:24:31 +, KeyTag 44630, Signer-Name: me






0 DNSKEY RR found









Zone: www.tinminnow.me

www.tinminnow.me
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.tinminnow.me
•  ns1.gandi.net

tinminnow.me
•  ns-133-c.gandi.net / node-berlin1
217.70.187.134
Newark/New Jersey/United States (US) - GANDI is an ICANN accredited registrar		•

• 
2604:3400:aaac::86
Ashburn/Virginia/United States (US) - Gandi SAS		•

•  ns-186-b.gandi.net / node-berlin1
213.167.230.187
Newark/New Jersey/United States (US) - Gandi SAS		•

• 
2001:4b98:aaab::bb
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar		•

•  ns-52-a.gandi.net / node-berlin1
173.246.100.53
Ashburn/Virginia/United States (US) - Gandi SAS		•

• 
2001:4b98:aaaa::35
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar		•
me
•  a0.nic.me / ns009b.app10.mia2.afilias-nst.info
•

•  a2.nic.me / 2.ber.pch
•

•  b0.nic.me / ns009b.app25.ams2.afilias-nst.info
•

•  b2.nic.me / 4.fra.pch
•

•  c0.nic.me / ns009a.app1.ams2.afilias-nst.info
•

 

4. SOA-Entries


Domain:me
Zone-Name:
Primary:ns.nic.me
Mail:noc.afilias-nst.info
Serial:2010799382
Refresh:3600
Retry:3600
Expire:3600000
TTL:8400
num Entries:5


Domain:tinminnow.me
Zone-Name:
Primary:ns1.gandi.net
Mail:hostmaster.gandi.net
Serial:1565889654
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:6


Domain:www.tinminnow.me
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://tinminnow.me/
140.82.59.163
301
https://tinminnow.me/

0.483
A
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:09 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://tinminnow.me/

• http://tinminnow.me/
2a05:f480:1400:674:5400:2ff:fe38:db91
301
https://tinminnow.me/

0.043
A
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:09 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://tinminnow.me/

• https://tinminnow.me/
140.82.59.163
200


3.284
A
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:09 GMT
Content-Type: text/html
Content-Length: 57
Last-Modified: Thu, 15 Aug 2019 18:55:18 GMT
Connection: close
ETag: "5d55aa96-39"
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Accept-Ranges: bytes

• https://tinminnow.me/
2a05:f480:1400:674:5400:2ff:fe38:db91
200


3.120
A
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:13 GMT
Content-Type: text/html
Content-Length: 57
Last-Modified: Thu, 15 Aug 2019 18:55:18 GMT
Connection: close
ETag: "5d55aa96-39"
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Accept-Ranges: bytes

• http://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
140.82.59.163
301
https://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.037
A
Visible Content:
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:16 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a05:f480:1400:674:5400:2ff:fe38:db91
301
https://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.043
A
Visible Content:
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:16 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

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

404


3.110
A
Not Found
Visible Content:
Server: nginx/1.15.9 (Ubuntu)
Date: Fri, 16 Aug 2019 10:23:16 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

 

7. Comments


1. General Results, most used to calculate the result

Aname "tinminnow.me" is domain, public suffix is "me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro"
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 https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 63072000 seconds = 730 days
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (3 urls)
https://tinminnow.me/ 140.82.59.163


Url with incomplete Content-Type - header - missing charset
https://tinminnow.me/ 2a05:f480:1400:674:5400:2ff:fe38:db91


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


Url with incomplete Content-Type - header - missing charset
Ahttp://tinminnow.me/ 140.82.59.163
301
https://tinminnow.me/
Correct redirect http - https with the same domain name
Ahttp://tinminnow.me/ 2a05:f480:1400:674:5400:2ff:fe38:db91
301
https://tinminnow.me/
Correct redirect http - https with the same domain name

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.gandi.net: 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
https://tinminnow.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
3.110 seconds
Warning: 404 needs more then one second
ADuration: 50836 milliseconds, 50.836 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
tinminnow.me
140.82.59.163
443
ok
Tls12
DiffieHellman
2048
Aes256
256
Sha384
supported
ok
tinminnow.me
140.82.59.163
443
ok
Tls12

DiffieHellman
2048
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
Chain - incomplete

1CN=tinminnow.me


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


tinminnow.me
2a05:f480:1400:674:5400:2ff:fe38:db91
443
ok
Tls12
DiffieHellman
2048
Aes256
256
Sha384
supported
ok

tinminnow.me
2a05:f480:1400:674:5400:2ff:fe38:db91
443
ok
Tls12

DiffieHellman
2048
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
Chain - incomplete

1CN=tinminnow.me


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


tinminnow.me
tinminnow.me
443
ok
Tls12
DiffieHellman
2048
Aes256
256
Sha384
supported
ok

tinminnow.me
tinminnow.me
443
ok
Tls12

DiffieHellman
2048
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
Chain - incomplete

1CN=tinminnow.me


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

 

9. Certificates

1.
1.
CN=tinminnow.me
15.08.2019
13.11.2019
2012 days expired		tinminnow.me - 1 entry
1.
1.
CN=tinminnow.me
15.08.2019

13.11.2019
2012 days expired


tinminnow.me - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:040F0AF6647EBD58926A3F9C62ED8AD76A0A
Thumbprint:D11C65D9A29CAE56F230DD23DF9713C7A13CD7DA
SHA256 / Certificate:9edom3272bgM/En/cKAtSL++jUolI3u+NCXv4ZBdljY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):cc99edca38c3609b8396153f87bf86fd9f13ef49f106dd1faf6c47e6c620d8e8
SHA256 hex / Subject Public Key Information (SPKI):cc99edca38c3609b8396153f87bf86fd9f13ef49f106dd1faf6c47e6c620d8e8
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
1522 days expired

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

17.03.2021
1522 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
1325 days expired

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

30.09.2021
1325 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)

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

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

 

12. 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
tinminnow.me
0

no CAA entry found
1
0
me
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tinminnow.me
protonmail-verification=055271909b5046ac5e4af700a2417e6f120cd217
ok
1
0
tinminnow.me
v=spf1 include:_spf.protonmail.ch mx ~all
ok
1
0
_acme-challenge.tinminnow.me

Name Error - The domain name does not exist
1
0
_acme-challenge.tinminnow.me.tinminnow.me

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=048784b5-3568-4540-a1c4-5255ba2f95ac

 

Last Result: https://check-your-website.server-daten.de/?q=tinminnow.me - 2019-08-16 12:22:41

 

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

 

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

 

 

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