Skikk.eu Laptop Samenstellen | SKIKK - Creëer jouw ideale laptop of mini pc op maat

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to 'AS8192 - AS8523'

as-block: AS8192 - AS8523
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by: RIPE-NCC-HM-MNT
created: 2010-05-11T11:44:46Z
last-modified: 2014-02-24T13:15:16Z
source: RIPE

% Information related to 'AS8315'

% Abuse contact for 'AS8315' is 'abuse@amsio.com'

aut-num: AS8315
as-name: AMSIO
remarks: Amsio Backbone
remarks: https://www.amsio.com
remarks: ==============================================================
remarks: Please find our peering details at
remarks: http://as8315.peeringdb.com/
remarks: ==============================================================
remarks: We have an open peering policy and would like to peer with
remarks: you. Please send requests to peering@amsio.com.
remarks: ==============================================================
remarks: NOC: noc@amsio.com
remarks: Abuse: abuse@amsio.com
remarks: ==============================================================
remarks: We share the view that for many networks ( including ours:-) )
remarks: only some abstraction of the actual routing policy should/can
remarks: be published in the IRR.
remarks: Right now we are abstracting to a very essential minimum.
remarks: the most important and helpful use of the IRR is
remarks: to publish what a network will announce to peers and upstream
remarks: we are providing that by means of the AS-set AS8315:AS-AMSIO
remarks: which we have been keeping up to date all the time
remarks: we encourage all our neighbors to define and maintain an
remarks: AS-set to describe their announcements, and to register
remarks: all the routes (and have their customers do so as well)
import: from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered...
remarks: we maintain a list of what our neighbors have told us
remarks: about their announcements towards AS8315 - in terms of
remarks: AS-set (preferred), AS number, route-set
remarks: (and the IRR database used to publish)
remarks: in fact we apply route filters based on this
remarks: for all neighbors - as far as feasible
remarks: for data published through the RIPE routing registry
remarks: we generate filters automatically
remarks: we consider the integration of RIR and routing registry data
remarks: and the application of RPSS authorization a great feature
remarks: of the RIPE routing registry
remarks: unfortunately this benefit is not available with any
remarks: other IRR database that we know of...
remarks: and some of the IRR databases allow essentially any garbage
remarks: to be registered without any control - making those databases
remarks: quite useless...
export: to AS8315:AS-CUSTOMERS announce ANY # but don't publish that list; in general - if they ask for less, we can do
export: to AS-ANY announce AS8315:AS-AMSIO # for peers and others... for backwards compatibility the older AS-ARGEWEB will be kept around for some more time - defined using just members: AS8315:AS-AMSIO please convert to AS8315:AS-AMSIO if you are still using the old AS-ARGEWEB
remarks: customers are strongly encouraged to define and maintain
remarks: an AS-set that we will include in the definition
remarks: of AS8315:AS-AMSIO (if we are told the name)
remarks: this will be sufficient to have our peers accept the routes
remarks: in any case peers - and any network in the Internet -
remarks: is free to apply some selective policy (e.g. prefix
remarks: length based)
remarks: but we do not think that any such selective policy
remarks: will be based on details of our routing policy omitted
remarks: from this aut-num: object
remarks: unfortunately some customers do not provide usable IRR data;
remarks: we will NOT add to the uncontrolled garbage in the IRR by
remarks: proxy registering in some database that requires no
remarks: authorization
remarks: we advise customers that routes without IRR registration
remarks: and not covered by AS8315:AS-AMSIO may receive less than
remarks: full support by some of our peer networks and other
remarks: parts of the Internet
remarks: ==============================================================
remarks: IPv6 we do/publish essentially the same like for IPv4
mp-import: afi ipv6.unicast from AS-ANY accept ANY # heavy abstraction... neither peering promiscuously nor accepting all junk routes offered...
mp-export: afi ipv6.unicast to AS8315:AS-CUSTOMERS-V6 announce ANY # but don't publish that list; in general - if they ask for less, we can do
mp-export: afi ipv6.unicast to AS-ANY announce AS8315:AS-AMSIO-V6 # for peers and others...
remarks: ==============================================================
org: ORG-AB31-RIPE
admin-c: ABNO3-RIPE
tech-c: ABNO3-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: AMSIO-MNT
created: 2006-01-05T09:59:28Z
last-modified: 2018-02-14T07:31:02Z
source: RIPE

organisation: ORG-AB31-RIPE
org-name: Amsio B.V.
org-type: LIR
address: Postbus 505
address: 3140AM
address: Maassluis
address: NETHERLANDS
phone: +31888007555
fax-no: +31888007501
admin-c: RvdZ8-RIPE
admin-c: OvdL5-RIPE
tech-c: RvdZ8-RIPE
abuse-c: ABRO2-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: AMSIO-MNT
mnt-by: RIPE-NCC-HM-MNT
mnt-by: AMSIO-MNT
created: 2010-05-10T10:59:12Z
last-modified: 2016-06-17T11:27:22Z
source: RIPE # Filtered

role: Amsio BV - Network Operators
address: Noordzee 10C
address: 3144DB Maassluis
address: The Netherlands
nic-hdl: ABNO3-RIPE
tech-c: SK3127-RIPE
tech-c: OvdL5-RIPE
tech-c: RvdZ8-RIPE
admin-c: GvL13-RIPE
admin-c: RvdZ8-RIPE
mnt-by: AMSIO-MNT
created: 2018-02-14T07:02:35Z
last-modified: 2018-02-14T07:03:26Z
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.91.2 (HEREFORD)

% The WHOIS service offered by EURid and the access to the records
% in the EURid WHOIS database are provided for information purposes
% only. It allows persons to check whether a specific domain name
% is still available or not and to obtain information related to
% the registration records of existing domain names.
%
% EURid cannot, under any circumstances, be held liable in case the
% stored information would prove to be wrong, incomplete or not
% accurate in any sense.
%
% By submitting a query you agree not to use the information made
% available to:
%
% - allow, enable or otherwise support the transmission of unsolicited,
% commercial advertising or other solicitations whether via email or
% otherwise;
% - target advertising in any possible way;
%
% - to cause nuisance in any possible way to the registrants by sending
% (whether by automated, electronic processes capable of enabling
% high volumes or other possible means) messages to them.
%
% Without prejudice to the above, it is explicitly forbidden to extract,
% copy and/or use or re-utilise in any form and by any means
% (electronically or not) the whole or a quantitatively or qualitatively
% substantial part of the contents of the WHOIS database without prior
% and explicit permission by EURid, nor in any attempt hereof, to apply
% automated, electronic processes to EURid (or its systems).
%
% You agree that any reproduction and/or transmission of data for
% commercial purposes will always be considered as the extraction of a
% substantial part of the content of the WHOIS database.
%
% By submitting the query you agree to abide by this policy and accept
% that EURid can take measures to limit the use of its WHOIS services
% in order to protect the privacy of its registrants or the integrity
% of the database.
%
% The EURid WHOIS service on port 43 (textual whois) never
% discloses any information concerning the registrant.
% Registrant and on-site contact information can be obtained through use of the
% webbased WHOIS service available from the EURid website www.eurid.eu
%
% WHOIS skikk.eu
Domain: skikk.eu
Script: LATIN

Registrant:
NOT DISCLOSED!
Visit www.eurid.eu for webbased WHOIS.

On-site(s):
NOT DISCLOSED!
Visit www.eurid.eu for webbased WHOIS.

Registrar:
Name: Registrar.eu
Website: https://www.openprovider.com

Name servers:
ns2.laptopplus.nl
ns1.laptopplus.nl

Keys:
flags:KSK protocol:3 algorithm:RSA_SHA256 pubKey:AwEAAffq/y8g65+7f8oQbF2hU+01M9LhJXSuNxZUpPYEaXf9qHYeNRKGRAJvU7Yeaw03qmdtQMdjxLC6k/u2TxCCTe7y99ca5TyUWOSks52hsM4B5bvpoLRKdWICERM6Uv+KsV/2nrE+7VqjC7rv8nga7VboBoGIu379zO511RGRxpxp6ZmleKEUXmv8fvNmU/3bRdXI5yn2t14LPSHWpD7wppDVNLgBBzWosGcSJU+Nz/oCDzvM6KqezCLP2Hg0KzQY0a6VIJdqg8lskLN4PD5Fop1ULh71+D0qK4Zb0UYWpgrJt2HDzA6oZEYTpzW+Xy/z58rVnNL9VTbdVZ4Suf8q1vE=

Please visit www.eurid.eu for more info.