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


 

 

A

 

Top config

 

Checked:
11.04.2019 14:57:52

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
namalelaki.com
A
206.189.145.95
Hostname: lelaki.namalelaki.com
yes
2
0

AAAA

yes


www.namalelaki.com
CNAME
namalelaki.com
yes
1
0

A
206.189.145.95
Hostname: lelaki.namalelaki.com
yes


 

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 25266, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.05.2019, 00:00:00 +, Signature-Inception: 11.04.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: com

com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.04.2019, 05:00:00 +, Signature-Inception: 11.04.2019, 04:00:00 +, KeyTag 25266, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 3800, Flags 256






Public Key with Algorithm 8, KeyTag 16883, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.04.2019, 18:25:33 +, Signature-Inception: 02.04.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com






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






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



Zone: namalelaki.com

namalelaki.com
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 "bf1u3frit36bej91nqlg9ndm6vi41cev" between the hashed NSEC3-owner "bf1ttjfb52nabckup5nrqd6uacu23e4q" and the hashed NextOwner "bf1uron6uk922uihdidoicl2i7ieaa71". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner bf1ttjfb52nabckup5nrqd6uacu23e4q.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 17.04.2019, 05:21:42 +, Signature-Inception: 10.04.2019, 04:11:42 +, KeyTag 16883, Signer-Name: com






0 DNSKEY RR found









Zone: www.namalelaki.com

www.namalelaki.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
namalelaki.com
  will.ns.cloudflare.com / 67m25
173.245.59.149

 
2400:cb00:2049:1::adf5:3b95

  zita.ns.cloudflare.com / 67m27
173.245.58.243

 
2400:cb00:2049:1::adf5:3af3
com
  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

 

4. SOA-Entries


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1554987453
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1554987463
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


Domain:namalelaki.com
Zone-Name:
Primary:will.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2030664471
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:4


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://namalelaki.com/
206.189.145.95
301
https://namalelaki.com/

0.514
A
Date: Thu, 11 Apr 2019 12:58:12 GMT
Server: Apache/2.4.29 (Ubuntu)
Location: https://namalelaki.com/
Content-Length: 311
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.namalelaki.com/
206.189.145.95
301
https://www.namalelaki.com/

0.520
A
Date: Thu, 11 Apr 2019 12:58:12 GMT
Server: Apache/2.4.29 (Ubuntu)
Location: https://www.namalelaki.com/
Content-Length: 319
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://www.namalelaki.com/
206.189.145.95
301
https://namalelaki.com/

2.517
A
Date: Thu, 11 Apr 2019 12:58:17 GMT
Server: Apache/2.4.29 (Ubuntu)
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding,Cookie
X-Redirect-By: WordPress
Location: https://namalelaki.com/
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Expires: Thu, 11 Apr 2019 13:58:17 GMT
X-XSS-Protection: 1; mode=block
X-UA-Compatible: IE=Edge,chrome=1
Pragma: no-cache
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://namalelaki.com/
206.189.145.95
200


3.020
A
Date: Thu, 11 Apr 2019 12:58:14 GMT
Server: Apache/2.4.29 (Ubuntu)
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding,Cookie
Link: <https://wp.me/aTdvL>; rel=shortlink
X-Mod-Pagespeed: 1.13.35.2-0
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Accept-Ranges: none
X-XSS-Protection: 1; mode=block
X-UA-Compatible: IE=Edge,chrome=1
Pragma: no-cache
Content-Length: 41374
Connection: close
Content-Type: text/html; charset="UTF-8"

• http://namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
206.189.145.95
301
https://namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.537
A
Visible Content:
Date: Thu, 11 Apr 2019 12:58:19 GMT
Server: Apache/2.4.29 (Ubuntu)
Location: https://namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 380
Connection: close
Content-Type: text/html; charset=iso-8859-1

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

0.540
A
Visible Content:
Date: Thu, 11 Apr 2019 12:58:19 GMT
Server: Apache/2.4.29 (Ubuntu)
Location: https://www.namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 388
Connection: close
Content-Type: text/html; charset=iso-8859-1

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

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

2.240
A
Visible Content:
Date: Thu, 11 Apr 2019 12:58:23 GMT
Server: Apache/2.4.29 (Ubuntu)
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding,Cookie
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
X-Redirect-By: WordPress
Location: https://namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-XSS-Protection: 1; mode=block
X-UA-Compatible: IE=Edge,chrome=1
Pragma: no-cache
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

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

404


2.274
A
Not Found
Visible Content:
Date: Thu, 11 Apr 2019 12:58:20 GMT
Server: Apache/2.4.29 (Ubuntu)
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding,Cookie
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Link: <https://namalelaki.com/wp-json/>; rel="https://api.w.org/"
X-XSS-Protection: 1; mode=block
X-UA-Compatible: IE=Edge,chrome=1
Pragma: no-cache
Content-Length: 7855
Connection: close
Content-Type: text/html; charset=UTF-8

 

7. Comments


1. General Results, most used to calculate the result

Aname "namalelaki.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
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: HSTS max-age is long enough, 31536000 seconds = 365 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://namalelaki.com/ 206.189.145.95
301
https://namalelaki.com/
Correct redirect http - https with the same domain name
Ahttp://www.namalelaki.com/ 206.189.145.95
301
https://www.namalelaki.com/
Correct redirect http - https with the same domain name

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
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://namalelaki.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.274 seconds
Warning: 404 needs more then one second
ADuration: 38920 milliseconds, 38.920 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
namalelaki.com
206.189.145.95
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok
namalelaki.com
206.189.145.95
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=namalelaki.com


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


www.namalelaki.com
206.189.145.95
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok

www.namalelaki.com
206.189.145.95
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=namalelaki.com


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


namalelaki.com
namalelaki.com
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok

namalelaki.com
namalelaki.com
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=namalelaki.com


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


www.namalelaki.com
www.namalelaki.com
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok

www.namalelaki.com
www.namalelaki.com
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=namalelaki.com


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

 

9. Certificates

1.
1.
CN=namalelaki.com
11.04.2019
10.07.2019
1974 days expired
namalelaki.com, www.namalelaki.com - 2 entries
1.
1.
CN=namalelaki.com
11.04.2019

10.07.2019
1974 days expired


namalelaki.com, www.namalelaki.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03AFE0B61AA2F3AF0D3C3F81BCD56FFAAC4E
Thumbprint:5BB62C8BD1A3580F45F92C56EA403F243E881B6D
SHA256 / Certificate:FzFaEV9IMMZSl05SbE4gjyEv/8JJ4w0eGVHusBTCdmE=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):e3eec45911c2101792d8af9b4243af18b81c7bdd24cff5c4b5d62826648c37f5
SHA256 hex / Subject Public Key Information (SPKI):e3eec45911c2101792d8af9b4243af18b81c7bdd24cff5c4b5d62826648c37f5
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
1358 days expired


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

17.03.2021
1358 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
1161 days expired


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

30.09.2021
1161 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 CRT - CT-Log entries found

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

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
www.namalelaki.com



1
0
namalelaki.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
namalelaki.com
ca3-767fb7b364bc42239c56b2e4bd7fd089
ok
1
0
www.namalelaki.com
ca3-767fb7b364bc42239c56b2e4bd7fd089
ok
1
0
_acme-challenge.namalelaki.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.namalelaki.com

Name Error - The domain name does not exist
1
0
_acme-challenge.namalelaki.com.namalelaki.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.namalelaki.com.www.namalelaki.com

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=7acc1b5f-9a44-44dc-8a62-ec421bfd8746

 

Last Result: https://check-your-website.server-daten.de/?q=namalelaki.com - 2019-04-11 14:57:52

 

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

 

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