Abf-hannover.de abf Hannover | Messe für Reisen, Caravaning & Freizeit
31. Januar bis 4. Februar 2024 in Hannover | Freuen Sie sich auf einen einzigartigen Mix aus Reise & Urlaub, Caravaning & Camping, Vanlife, Fahrrad, O...
Over the time abf-hannover.de has been ranked as high as 54,700 in the world.
Abf-hannover.de receives about 60 unique visitors and 60 pageviews per day. The estimated value of abf-hannover.de is 0 USD. Each unique visitor makes about 1 pageviews on average.
Abf-hannover.de is registered under .DE top-level domain. Check other websites in .DE zone.
At the time of the last check (April 30, 2021) abf-hannover.de has an expired wildcard SSL certificate issued by T-Systems International GmbH (expired on August 24, 2021). Check other websites using SSL certificates issued by T-Systems International GmbH.
According to Google Safe Browsing, Google Safe Search and Symantec abf-hannover.de is quite a safe domain.
Mobile-Friendly test indicates that abf-hannover.de is well optimized for mobile and tablet devices, however website page loading time could be improved.
Alexa Rank shows how popular abf-hannover.de is in comparison with other sites. The most popular site has Alexa Rank equals 1. If abf-hannover.de has Alexa Rank equals 100,000, then it is in TOP 100,000 popular sites in the world. The rank is calculated using a combination of average daily visitors to abf-hannover.de and pageviews on abf-hannover.de over the past 3 months.
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 ConnectSafe evaluates abf-hannover.de for any unsafe and insecure content. The results are critical for families with young children.
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.
"abf-hannover.de" is not a phishing page.
"abf-hannover.de" does not install unwanted software.
"abf-hannover.de" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
McAfee assesses abf-hannover.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 abf-hannover.de for mature or inappropriate content, only security checks are evaluated.
The WOT calculates reputation of the abf-hannover.de. This reputation system receives ratings from users and information from third-party sources, assesses the abf-hannover.de for safety features and confirms, whether abf-hannover.de is suitable for children.
| Domain | *.abf-hannover.de |
| Issuer Organization | T-Systems International GmbH |
| Issuer | TeleSec ServerPass Class 2 CA |
| Algorithm | RSA-SHA256 |
| Valid form | 08/19/2020 |
| Expiration | 08/24/2021 |
| Signed | Certificate is not self signed |
| Additional Domains | *.abf-hannover.de abf-hannover.de |
Not Found
ASN ID: 3320
ASN Title: Deutsche Telekom AG
Last Update: 03/17/2024
% 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.
mnt-by: RIPE-NCC-HM-MNT
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
org: ORG-DTA2-RIPE
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
authorization
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
mnt-by: RIPE-NCC-END-MNT
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: RIPE-NCC-HM-MNT
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: abf-hannover.de
Status: connect
| Host | A Record | TTL |
|---|
| Host | MX Record | Priority | TTL |
|---|
| Host | NS Record | TTL |
|---|
| Host | TXT Record | TTL |
|---|
Last tested: 03/06/2019
| Total Resources | 71 |
| Number of Hosts | 12 |
| Static Resources | 57 |
| JavaScript Resources | 11 |
| CSS Resources | 7 |
Last tested: 03/06/2019
| Total Resources | 72 |
| Number of Hosts | 13 |
| Static Resources | 58 |
| JavaScript Resources | 11 |
| CSS Resources | 7 |
www.abf-hannover.net
www.abf-hannover.org
www.abf-hannover.info
www.abf-hannover.biz
www.abf-hannover.us
www.abf-hannover.mobi
www.bf-hannover.de
www.abf-hannover.de
www.qbf-hannover.de
www.aqbf-hannover.de
www.qabf-hannover.de
www.wbf-hannover.de
www.awbf-hannover.de
www.wabf-hannover.de
www.sbf-hannover.de
www.asbf-hannover.de
www.sabf-hannover.de
www.zbf-hannover.de
www.azbf-hannover.de
www.zabf-hannover.de
www.af-hannover.de
www.avf-hannover.de
www.abvf-hannover.de
www.avbf-hannover.de
www.agf-hannover.de
www.abgf-hannover.de
www.agbf-hannover.de
www.ahf-hannover.de
www.abhf-hannover.de
www.ahbf-hannover.de
www.anf-hannover.de
www.abnf-hannover.de
www.anbf-hannover.de
www.ab-hannover.de
www.abc-hannover.de
www.abfc-hannover.de
www.abcf-hannover.de
www.abd-hannover.de
www.abfd-hannover.de
www.abdf-hannover.de
www.abr-hannover.de
www.abfr-hannover.de
www.abrf-hannover.de
www.abt-hannover.de
www.abft-hannover.de
www.abtf-hannover.de
www.abg-hannover.de
www.abfg-hannover.de
www.abv-hannover.de
www.abfv-hannover.de
www.abfhannover.de
www.abf-annover.de
www.abf-bannover.de
www.abf-hbannover.de
www.abf-bhannover.de
www.abf-gannover.de
www.abf-hgannover.de
www.abf-ghannover.de
www.abf-yannover.de
www.abf-hyannover.de
www.abf-yhannover.de
www.abf-uannover.de
www.abf-huannover.de
www.abf-uhannover.de
www.abf-jannover.de
www.abf-hjannover.de
www.abf-jhannover.de
www.abf-nannover.de
www.abf-hnannover.de
www.abf-nhannover.de
www.abf-hnnover.de
www.abf-hqnnover.de
www.abf-haqnnover.de
www.abf-hqannover.de
www.abf-hwnnover.de
www.abf-hawnnover.de
www.abf-hwannover.de
www.abf-hsnnover.de
www.abf-hasnnover.de
www.abf-hsannover.de
www.abf-hznnover.de
www.abf-haznnover.de
www.abf-hzannover.de
www.abf-hanover.de
www.abf-habnover.de
www.abf-hanbnover.de
www.abf-habnnover.de
www.abf-hahnover.de
www.abf-hanhnover.de
www.abf-hahnnover.de
www.abf-hajnover.de
www.abf-hanjnover.de
www.abf-hajnnover.de
www.abf-hamnover.de
www.abf-hanmnover.de
www.abf-hamnnover.de
www.abf-hanbover.de
www.abf-hannbover.de
www.abf-hanhover.de
www.abf-hannhover.de
www.abf-hanjover.de
www.abf-hannjover.de
www.abf-hanmover.de
www.abf-hannmover.de
www.abf-hannver.de
www.abf-hanniver.de
www.abf-hannoiver.de
www.abf-hanniover.de
www.abf-hannkver.de
www.abf-hannokver.de
www.abf-hannkover.de
www.abf-hannlver.de
www.abf-hannolver.de
www.abf-hannlover.de
www.abf-hannpver.de
www.abf-hannopver.de
www.abf-hannpover.de
www.abf-hannoer.de
www.abf-hannocer.de
www.abf-hannovcer.de
www.abf-hannocver.de
www.abf-hannofer.de
www.abf-hannovfer.de
www.abf-hannofver.de
www.abf-hannoger.de
www.abf-hannovger.de
www.abf-hannogver.de
www.abf-hannober.de
www.abf-hannovber.de
www.abf-hannobver.de
www.abf-hannovr.de
www.abf-hannovwr.de
www.abf-hannovewr.de
www.abf-hannovwer.de
www.abf-hannovsr.de
www.abf-hannovesr.de
www.abf-hannovser.de
www.abf-hannovdr.de
www.abf-hannovedr.de
www.abf-hannovder.de
www.abf-hannovrr.de
www.abf-hannoverr.de
www.abf-hannovrer.de
www.abf-hannove.de
www.abf-hannovee.de
www.abf-hannovere.de
www.abf-hannoveer.de
www.abf-hannoved.de
www.abf-hannoverd.de
www.abf-hannovef.de
www.abf-hannoverf.de
www.abf-hannovefr.de
www.abf-hannovet.de
www.abf-hannovert.de
www.abf-hannovetr.de