Telepost.gl TELE |

% 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 'AS8771 - AS9128'

as-block: AS8771 - AS9128
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:47Z
last-modified: 2014-02-24T13:15:16Z
source: RIPE

% Information related to 'AS8818'

% Abuse contact for 'AS8818' is 'gl-npl@tele.gl'

aut-num: AS8818
as-name: UNSPECIFIED
org: ORG-TG8-RIPE
remarks:
remarks: - RFC1918 and other reserved networks and subnets are
remarks: not permitted.
remarks:
remarks: - Advertisements with reserved ASes in the path
remarks: (ie 64512 - 65535) are not permitted.
remarks:
remarks: - Prefixes shorter than /8 or longer than /24 are
remarks: not permitted.
remarks:
remarks: - Advertisements containing the AS of a network with
remarks: which we have a non-customer peering relationship
remarks: are not permitted (ie customers are not allowed
remarks: to advertise transit for other Tier 1 or 2 ISPs).
remarks:
remarks: - All customer peering sessions are prefix-filtered
remarks: inbound using data from any known public registry.
remarks:
remarks: - Prefixes not matching the per-peer import policy
remarks: as documented above are not permitted.
remarks:
remarks: - Localpref will be set to 100 by default
remarks:
remarks: - A hard limit is placed on the number of routes a peer
remarks: is allowed to announce to us. (Maximum-prefixes)
remarks:
remarks: - MEDs are overwritten unless special arrangements
remarks: have been made.
remarks:
remarks: - Suppression and prepend actions as outlined in the
remarks: community list below are taken for announcements to
remarks: non-customer peers.
remarks:
remarks:
import: from AS3292 accept ANY
import: from AS3356 accept ANY
import: from AS174 accept ANY
import: from AS11260 accept ANY
import: from AS25509 accept AS34678
export: to AS25509 announce ANY
export: to AS3292 announce AS8818
export: to AS3257 announce AS8818
export: to AS3356 announce AS8818
export: to AS174 announce AS8818
export: to AS11260 announce AS8818
admin-c: JFS2-RIPE
tech-c: JFS2-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: AS8818-MNT
created: 1970-01-01T00:00:00Z
last-modified: 2017-11-15T09:13:32Z
source: RIPE

organisation: ORG-TG8-RIPE
org-name: Tele Greenland
org-type: LIR
address: P.O.Box 1002
address: DK-3900
address: Nuuk
address: GREENLAND
phone: +299 32 12 55
fax-no: +299 32 29 66
abuse-c: AR15427-RIPE
mnt-ref: AS8818-MNT
mnt-ref: RIPE-NCC-HM-MNT
mnt-by: RIPE-NCC-HM-MNT
mnt-by: AS8818-MNT
created: 2004-04-17T11:24:35Z
last-modified: 2017-10-09T11:03:19Z
source: RIPE # Filtered
admin-c: CBJ22-RIPE
admin-c: JFS2-RIPE

person: John Frederik Siegstad
address: postbox 1002
address: dk-3900 nuuk
phone: +299 32 12 55
fax-no: +299 32 52 55
nic-hdl: JFS2-RIPE
mnt-by: GL-DOMREG
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-22T00:39:53Z
source: RIPE # Filtered

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

Domain Name: TELEPOST.GL
Registry Domain ID: D327737944-CNIC
Registrar WHOIS Server: whois.nic.gl
Registrar URL: https://www.tusass.gl/
Updated Date: 2023-08-31T17:00:37.0Z
Creation Date: 2001-06-26T02:00:00.0Z
Registry Expiry Date: 2032-09-19T23:59:59.0Z
Registrar: Tusass
Registrar IANA ID: 9999
Domain Status: ok https://icann.org/epp#ok
Registrant Email: https://whois.nic.gl/contact/telepost.gl/registrant
Admin Email: gl-admin@tusass.gl
Tech Email: gl-admin@tusass.gl
Name Server: A.NS.TUSASS.GL
Name Server: B.NS.TUSASS.GL
DNSSEC: unsigned
Registrar Abuse Contact Email: gl-admin@tusass.gl
Registrar Abuse Contact Phone: +44.123456789
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-11-13T07:30:57.0Z > IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit
https://www.centralnicregistry.com/support/rdap