Titre:dc :: news
La description :duckcorp website...
Server:Apache...
L'adresse IP principale: 193.200.42.177,Votre serveur France,Paris ISP:Hivane TLD:org Code postal:fr
Ce rapport est mis à jour en 24-Sep-2018
Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations. Notre service GeoIP a trouvé l'hôte duckcorp.org.Actuellement, hébergé dans France et son fournisseur de services est Hivane .
Latitude: | 48.853408813477 |
Longitude: | 2.348799943924 |
Pays: | France (fr) |
Ville: | Paris |
Région: | Ile-de-France |
ISP: | Hivane |
domaine | Titre |
---|
Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé Apache contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.
Content-Length: | 3914 |
Upgrade: | h2 |
Content-Security-Policy: | default-src 'none'; img-src 'self' https://webstats.duckcorp.org/piwik.php; script-src 'self' https://webstats.duckcorp.org/piwik.js; style-src 'self' |
X-Content-Type-Options: | nosniff |
Content-Encoding: | gzip |
Accept-Ranges: | bytes |
Vary: | Accept-Encoding |
Keep-Alive: | timeout=5, max=100 |
Server: | Apache |
Last-Modified: | Sun, 23 Sep 2018 01:33:06 GMT |
Connection: | Upgrade, Keep-Alive |
ETag: | "3103-5767fdab87880-gzip" |
Date: | Mon, 24 Sep 2018 12:54:33 GMT |
Content-Type: | text/html |
soa: | ns1.duckcorp.org. hostmaster.duckcorp.org. 2018092404 3600 3600 2419200 3600 |
ns: | ns3.duckcorp.org. ns1.duckcorp.org. ns2.duckcorp.org. ns1.hivane.net. |
ipv4: | IP:193.200.42.177 ASN:34019 OWNER:HIVANE, FR Country:FR |
ipv6: | 2001:67c:1740:9001::c1c8:2ab1//34019//HIVANE, FR//FR |
txt: | "google-site-verification=wltvlM-jM6LfKuHPBHDmz5nH3by2tc8cDgSm56IKHzw" "DuckCorp" |
mx: | MX preference = 10, mail exchanger = mx4.duckcorp.org. MX preference = 10, mail exchanger = mx1.duckcorp.org. MX preference = 20, mail exchanger = mx2.hivane.net. MX preference = 20, mail exchanger = mx0.hivane.net. |
news who are we? featured projects contribute contact us public srv: projects / vcs debian repository ntp (stratum 2) dico user srv: stuffcloud webmail / lists irc on web / irc stats documentation: general wiki / users' wiki infrastructure [news] [activity] projects activities [ 2018-09-22 03:37 +0200 ] wip duckcorp infrastructure> revision 839ddca2 (duckcorp-infra): improve multihoming script [ 2018-09-21 03:47 +0200 ] wip duckcorp infrastructure> revision fd806bc1 (duckcorp-infra): updated logcheck rules #5 [ 2018-09-20 17:54 +0200 ] wip duckcorp infrastructure> revision bee22da5 (duckcorp-infra): updated logcheck rules #4 [ 2018-09-20 10:59 +0200 ] wip duckcorp infrastructure> revision b5823ada (ansible-role-zabbix): add mailman3 service [ 2018-09-20 09:25 +0200 ] wip duckcorp infrastructure> revision 5eb4ca9b (duckcorp-infra): remove user laura [ 2018-09-19 21:23 +0200 ] wip bip> bug #636 (new): build fails with gcc 8 due to format truncation errors [ 2018-09-19 09:18 +0200 ] wip duckcorp infrastructure> revision 0324b891 (duckcorp-infra): updated logcheck rules #3 (typo) [ 2018-09-19 05:01 +0200 ] wip duckcorp infrastructure> revision 38f631d1 (duckcorp-infra): new ssh keys for duck [ 2018-09-19 04:55 +0200 ] wip duckcorp infrastructure> revision ad65fac1 (duckcorp-infra): merge branch 'logcheck_update_2' [ 2018-09-15 17:49 +0200 ] wip duckcorp infrastructure> revision 43cf60f3 (duckcorp-infra): updated logcheck rules #2 2018-06-27 04:44 +0200 word from the admin team [archives] « mail revamping #2 » quack, mail system redundancy our old antispam system has been shutdown and toushirou has been promoted to full mx1/mda/maa. this means we now have two machine receiving mails, filtering spam and synchronizing with each-other (sieve rules and antispam learning are synced too). i just updated the dns records so that {smtp,mail,imap,pop,sieve}.duckcorp.org now balance between the two. so if one machine is down, you should be able to retry to reach your mail on the second machine. the webmail is currently not redundant but we’re working on it. the mailing-lists will stay on orfeo as there is currently no way to make this service redundant. note about the antispam we had some user questions so i wanted to clarify a few things. the new learning system is very similar to the previous one. the big change is: from now on all learning is shared between users. this means you benefits from spam caught by other users but it makes the learning less personalized. it is difficult to evaluate what’s best but per-user learning made the system very complex and was very resource intensive so we decided to try the shared method. many well known big companies also use shared training, so that new users don’t start with a blank system which would need weeks or months to be well trained and it seems to work quite well. another important point is how to train the system. we simplified the old system and the new one does not have a web interface for users anyway. the ‘junk’ folder (your mail client may translate the name) is used to collect discovered spam. if you move mails into it you inform the system it is a spam it should have caught. if you move a mail out of it then you inform the system it made a mistake and this is not a spam. to get detected spam automatically put into the ‘junk’ folder there is a default sieve filter. but if you added your own filters, then you need to include the default rule into your configuration as explained here: https://users.duckcorp.org/index.php/services/mail this was done to allow users to override the default rule if they wanted another workflow. we’re wondering if this has any real application and thinking about making this rule compulsory (processed before any user filters). your input on this matter is welcome. \_o< activism special support sponsors this work is licensed under a creative commons attribution-share alike 3.0 license . © 2000-2015 duckcorp | generated by nanoc on 2018-09-23 03:33:06 +0200.
https://www.duckcorp.org/04_contact.html
https://www.duckcorp.org/02_featured_projects.html
https://www.duckcorp.org/01_who_are_we.html
https://www.duckcorp.org/03_contribute.html
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
WHOIS LIMIT EXCEEDED - SEE WWW.PIR.ORG/WHOIS FOR DETAILS
REFERRER http://www.pir.org/
REGISTRAR Public Interest Registry
SERVERS
SERVER org.whois-servers.net
ARGS duckcorp.org
PORT 43
TYPE domain
RegrInfo
REGISTERED unknown
DOMAIN
NAME duckcorp.org
NSERVER
NS1.HIVANE.NET 193.17.192.70
NS2.DUCKCORP.ORG 193.200.42.177
NS3.DUCKCORP.ORG 213.215.11.164
NS1.DUCKCORP.ORG 193.200.43.105
La liste suivante vous montre les fautes d'orthographe possibles des internautes pour le site Web recherché.