Micropayment.de ranking shows that the page is at position 167,087 over the world, while the bulk of its audience is from Germany, where it ranks 8,740.
It is beneficial to micropayment.de that their hosting company Deutsche Telekom AG servers are located in Germany, as that reduces page load time for the majority of their users. See the list of other webpages hosted on Deutsche Telekom AG servers.
In terms of rank-to-traffic ratio, micropayment.de has 2,431 unique users per day, viewing 4,416 pages. The rank based value of micropayment.de is 78,919 USD. Every user makes 1.93 pageviews on average.
Micropayment.de boasts a link base consisting of 409 referring domains and 489 external backlinks, as revealed by the data obtained from web network scanning.
Micropayment.de top-level domain belongs to .DE domain zone. Check other webpages in .DE zone.
According the last verification test in October 10, 2024, micropayment.de has a valid and up-to-date wildcard SSL certificate issued by DigiCert Inc , certificate expiration date: June 05, 2025. Click button “Update” SSL Information at the Safety Information section. Check the list of websites using SSL by DigiCert Inc.
Based on data from Google Safe Browsing, Google Safe Search, Symantec and Web of Trust micropayment.de is a fairly safe domain.
According the Mobile-Friendly test by Google micropayment.de is nice optimized for mobile devices and tablets, however the webpage speed could be improved.
Domain | *.micropayment.de |
Issuer Organization | DigiCert Inc |
Issuer | Thawte TLS RSA CA G1 |
Algorithm | RSA-SHA256 |
Valid form | 05/27/2024 |
Expiration | 06/05/2025 |
Signed | Certificate is not self signed |
Additional Domains |
*.micropayment.de micropayment.de |
Alexa Rank shows how popular micropayment.de is in comparison with other sites. The most popular site has Alexa Rank equals 1. If micropayment.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 micropayment.de and pageviews on micropayment.de over the past 3 months.
ASN ID: 3320
ASN Title: Deutsche Telekom AGLast Update: 07/22/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: micropayment.de
Status: connect
Host | A Record | TTL |
---|---|---|
micropayment.de | 193.159.183.234 | 10800 |
Host | MX Record | Priority | TTL |
---|---|---|---|
micropayment.de | smail.micropayment.de | 10 | 10800 |
micropayment.de | mail2.micropayment.de | 20 | 10800 |
Host | NS Record | TTL |
---|---|---|
micropayment.de | pns.dtag.de | 10800 |
micropayment.de | secondary006.dtag.net | 10800 |
Host | TXT Record | TTL |
---|---|---|
micropayment.de | v=spf1 mx -all | 86400 |
ns.service-url.de
TTL: 10800
Email address: postmaster.service-url.de
Serial: 2019081600
Refresh: 10800
Retry: 6000
Expire: 604800
Minimum: 43200
Last tested: 12/31/2016
Total Resources | 60 |
Number of Hosts | 5 |
Static Resources | 56 |
JavaScript Resources | 5 |
CSS Resources | 2 |
Last tested: 12/31/2016
Total Resources | 84 |
Number of Hosts | 6 |
Static Resources | 56 |
JavaScript Resources | 25 |
CSS Resources | 2 |