Whois GatewayBETA
This is a beta version of the Whois Gateway operated by ST47. It adds support for querying referral DNS servers, such as those provided by Cogent for their 38.0.0.0/8 range. This is done automatically when the provider supports it. The source code for this fork is maintained at GitHub.
IP address
2a01cb09b060b97c942425af873215b0.ipv6.abo.wanadoo.fr
geolite2Paris, Paris, Francegeo_ipinfoParis, Île-de-France, FRasn_registryRIPENCCasn_country_codeFRasn_cidr2a01:cb08::/30query2a01:cb09:b060:b97c:9424:25af:8732:15b0nets
nameFR-TELECOM-20051230descriptionOrange S.A.addressNonecityNonestateNonecountryFRpostal_codeNonecidr2a01:c000::/19range2a01:c000:: - 2a01:dfff:ffff:ffff:ffff:ffff:ffff:ffffcreated2005-12-30T11:11:04Zupdated2021-12-15T10:29:14ZhandleNoneemailsNone
asn3215asn_date2005-12-30asn_descriptionFrance Telecom - Orange, FRnirNone
Link this resulthttps://whois-referral.toolforge.org/gateway.py?lookup=true&ip=2A01:CB09:B060:B97C:9424:25AF:8732:15B0
Other tools
2A01:CB09:B060:B97C:9424:25AF:8732:15B0@Bullseye2A01:CB09:B060:B97C:9424:25AF:8732:15B0@Geolocation2A01:CB09:B060:B97C:9424:25AF:8732:15B0@GlobalContribs2A01:CB09:B060:B97C:9424:25AF:8732:15B0@ProxyChecker2A01:CB09:B060:B97C:9424:25AF:8732:15B0@Stalktoy
Sources
2A01:CB09:B060:B97C:9424:25AF:8732:15B0@AFRINIC2A01:CB09:B060:B97C:9424:25AF:8732:15B0@APNIC2A01:CB09:B060:B97C:9424:25AF:8732:15B0@ARIN2A01:CB09:B060:B97C:9424:25AF:8732:15B0@LACNIC2A01:CB09:B060:B97C:9424:25AF:8732:15B0@RIPENCC
Whois Gateway (source code, upstream, API) on Toolforge / Issues?
Network Working Group Zaw-Sing Su (SRI) Request for Comments: 819 Jon Postel (ISI) August 1982 The Domain Naming Convention for Internet User Applications 1. Introduction For many years, the naming convention "<user>@<host>" has served the ARPANET user community for its mail system, and the substring "<host>" has been used for other applications such as file transfer (FTP) and terminal access (Telnet). With the advent of network interconnection, this naming convention needs to be generalized to accommodate internetworking. A decision has recently been reached to replace the simple name field, "<host>", by a composite name field, "<domain>" [2]. This note is an attempt to clarify this generalized naming convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications. The following example illustrates the changes in naming convention: ARPANET Convention: Fred@ISIF Internet Convention: [email protected] The intent is that the Internet names be used to form a tree-structured administrative dependent, rather than a strictly topology dependent, hierarchy. The left-to-right string of name components proceeds from the most specific to the most general, that is, the root of the tree, the administrative universe, is on the right. The name service for realizing the Internet naming convention is assumed to be application independent. It is not a part of any particular application, but rather an independent name service serves different user applications. 2. The Structural Model The Internet naming convention is based on the domain concept. The name of a domain consists of a concatenation of one or more <simple names>. A domain can be considered as a region of jurisdiction for name assignment and of responsibility for name-to-address translation. The set of domains forms a hierarchy. Using a graph theory representation, this hierarchy may be modeled as a directed graph. A directed graph consists of a set
https://www.france.fr/
fi-ameli.png (236×90)
https://app.franceconnect.gouv.fr/images/fi-ameli.png
fi-laposte.png (316×72)
https://app.franceconnect.gouv.fr/images/fi-laposte.png
Vous êtes sûr ? Votre mobilisation est importante pour que les pétitions atteignent la victoire !
Sachez que vous pouvez vous désinscrire dès que vous le souhaitez.