Rlp.de rlp.de: Startseite . Internetportal des Landes Rheinland-Pfalz

Miteinander gut leben – Informationen über das Land Rheinland-Pfalz

Online Status

Server IP address resolved: Yes
Http response code: 200
Response time: 3.12 sec.
Last Checked: 04/22/2024

Rlp.de traffic volume is 7,425 unique daily visitors and their 14,107 pageviews. The web value rate of rlp.de is 243,703 USD. Each visitor makes around 2.03 page views on average.

By Alexa's traffic estimates rlp.de placed at 4,687 position over the world, while the largest amount of its visitors comes from Germany, where it takes 1,823 place.

Perfect for rlp.de that their data center (provided by company company Deutsche Telekom AG) is located in Germany, as that empowers most of the visitors to reduce the page load time. See the list of other web pages hosted by Deutsche Telekom AG.

Rlp.de registered under .DE top-level domain. Check other websites in .DE zone.

The last verification results, performed on (November 22, 2019) rlp.de show that rlp.de has an expired wildcard SSL certificate issued by DigiCert Inc (expired on August 05, 2020). Click “Refresh” button for SSL Information at the Safety Information section. Check the list of websites using SSL certificates issued by DigiCert Inc.

In accordance with Google Safe Browsing, Google Safe Search, Symantec and Web of Trust rlp.de is pretty a safe domain.

Relying Google MobileFriendly test rlp.de is well optimized for mobile and tablet devices, however web page loading speed may be improved.

Global Rank
Average Load Time
Links In Count
Website Value

Last Updated: 04/22/2024
Overall result - rlp.de is safe.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 03/21/2024
rlp.de is safe.
Norton ConnectSafe evaluates rlp.de for any unsafe and insecure content. The results are critical for families with young children.
Google Safe Search
Last Updated: 10/15/2016
rlp.de is safe.
SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.
Google Safe Browsing
Last Updated: 01/09/2019
rlp.de is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 02/22/2021
rlp.de is safe.
McAfee assesses rlp.de for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze rlp.de for mature or inappropriate content, only security checks are evaluated.
Web of Trust
Last Updated: 01/09/2019
rlp.de child safety is very good.
The WOT calculates reputation of the rlp.de. This reputation system receives ratings from users and information from third-party sources, assesses the rlp.de for safety features and confirms, whether rlp.de is suitable for children.

SSL Information
Issuer OrganizationDigiCert Inc
IssuerDigiCert SHA2 High Assurance Server CA
Valid form05/08/2017
SignedCertificate is not self signed
Additional Domains *.rlp.de
Server Location

ASN Information

ASN ID: 3320
ASN Title: Deutsche Telekom AG

Last Update: 10/02/2023

% 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 'AS3209 - AS3353'

as-block: AS3209 - AS3353
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
created: 2010-05-11T11:44:28Z
last-modified: 2014-02-24T13:15:16Z
source: RIPE

% Information related to 'AS3320'

% Abuse contact for 'AS3320' is 'auftrag@nic.telekom.de'

aut-num: AS3320
as-name: DTAG
descr: Internet service provider operations
remarks: peering coordinators for AS3320:
remarks: abuse reports should be sent to the contacts
listed in the registry entries for the IP address of the
offending host system
remarks: We share the view that for many networks (including ours:-)
only some abstraction of the actual routing policy should/can
be published in the IRR.
Right now we are abstracting to a very essential minimum.
remarks: the most important and helpful use of the IRR is
to publish what a network will announce to peers and upstream
# we are providing that by means of the AS-set AS3320:AS-DTAG
# which we have been keeping up to date all the time
remarks: we encourage all our neighbors to define and maintain an
AS-set to describe their announcements, and to register
all the routes (and have their customers do so as well)
import: # heavy abstraction hits! well, we are ...
from AS-ANY # neither peering promiscuously
accept ANY # nor accepting all junk routes offered...
remarks: we maintain a list of what our neighbors have told us
about their announcements towards AS3320 - in terms of
AS-set (preferred), AS number, route-set
(and the IRR database used to publish)
remarks: in fact we apply route filters based on this
for all neighbors - as far as feasible
remarks: for data published through the RIPE routing registry
we generate filters automatically
remarks: we consider the integration of RIR and routing registry data
and the application of RPSS authorization a great feature
of the RIPE routing registry
# unfortunately this benefit is not available with any
# other IRR database that we know of...
# and some of the IRR databases allow essentially any garbage
# to be registered without any control - making those databases
# quite useless...
export: to AS3320:AS-CUSTOMERS # but don't publish that list;
announce ANY # in general - if they ask for less, we can do
export: to AS-ANY # for peers and others...
announce AS3320:AS-DTAG
# for backwards compatibility the older AS-DTAG
# will be kept around for some more time -
# defined using just members: AS3320:AS-DTAG
# please convert to AS3320:AS-DTAG if you are still
# using the old AS-DTAG
remarks: customers are strongly encouraged to define and maintain
an AS-set that we will include in the definition
of AS3320:AS-DTAG (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 -
is free to apply some selective policy (e.g. prefix
length based)
# but we do not think that any such selective policy
# will be based on details of our routing policy omitted
# from this aut-num: object
remarks: unfortunately some customers do not provide usable IRR data;
we will NOT add to the uncontrolled garbage in the IRR by
proxy registering in some database that requires no
remarks: we advise customers that routes without IRR registration
and not covered by AS3320:AS-DTAG may receive less than
full support by some of our peer networks and other
parts of the Internet
remarks: ==============================================================
IPv6 we do/publish essentially the same like for IPv4
mp-import: afi ipv6.unicast # heavy abstraction...
from AS-ANY # neither peering promiscuously
accept ANY # nor accepting all junk routes offered...
mp-export: afi ipv6.unicast
to AS3320:AS-CUSTOMERS-V6 # but don't publish that list;
announce ANY # in general - if they ask for less, we can do
mp-export: afi ipv6.unicast
to AS-ANY # for peers and others...
announce AS3320:AS-DTAG-V6
remarks: ==============================================================
admin-c: RV32
tech-c: RV32
status: ASSIGNED
tech-c: BP32-RIPE
mnt-by: DTAG-RR
created: 1970-01-01T00:00:00Z
last-modified: 2017-11-15T09:13:45Z
source: RIPE

organisation: ORG-DTA2-RIPE
org-name: Deutsche Telekom AG
org-type: LIR
address: Eduard-Schopf-Allee 1
address: D-28217
address: Bremen
address: GERMANY
phone: +491607069891
fax-no: +494412344589
admin-c: DTAG-RIPE
admin-c: MR22061-RIPE
admin-c: UR661-RIPE
admin-c: SL7866-RIPE
admin-c: VZ56-RIPE
admin-c: SP8519-RIPE
admin-c: REIS1-RIPE
admin-c: HI56-RIPE
admin-c: PB4856-RIPE
admin-c: MBT1-RIPE
admin-c: BP32-RIPE
admin-c: LB470-RIPE
admin-c: ES4155-RIPE
admin-c: RV32
admin-c: PA3357-RIPE
admin-c: SB15220-RIPE
admin-c: KUNO2-RIPE
admin-c: HB3076-RIPE
admin-c: LF1459-RIPE
admin-c: KB6787-RIPE
abuse-c: DTAG3-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: DTAG-NIC
mnt-by: DTAG-NIC
created: 2004-04-17T11:12:44Z
last-modified: 2018-05-08T12:28:26Z
source: RIPE # Filtered

person: Berthold Paffrath
address: Deutsche Telekom AG, Internet Services
address: Postfach 2767
address: D-48014 Muenster
phone: +49 251 910 351
fax-no: +49 251 910 399
nic-hdl: BP32-RIPE
mnt-by: DTAG-RR
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-21T23:34:28Z
source: RIPE # Filtered

person: Ruediger Volk
address: Deutsche Telekom AG, Zentrum IOT
address: Postfach 2767
address: D-48014 Muenster
phone: +49 251 910 351
fax-no: +49 251 910 399
nic-hdl: RV32
mnt-by: DTAG-RR
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-21T23:34:30Z
source: RIPE # Filtered

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


Domain: rlp.de
Status: connect

DNS Records
HostA RecordTTL
HostMX RecordPriorityTTL
HostNS RecordTTL
HostTXT RecordTTL

TTL: 600
Email address: dnsadmin.nic.rlp.de
Serial: 2019080802
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum: 3600


Last tested: 05/30/2017

Desktop Speed

Desktop Resource Breakdown
Total Resources59
Number of Hosts3
Static Resources52
JavaScript Resources26
CSS Resources9

Last tested: 05/30/2017

Mobile Usability
Mobile Speed

Mobile Resource Breakdown
Total Resources59
Number of Hosts3
Static Resources52
JavaScript Resources26
CSS Resources9