Autonomous system
AS16072 FDD
Unclassified RIPE
Summary
First Data
finance business infrastructure
One netname says the block is for internal purposes, and it is announced to the whole internet.
What it's used for
- A payment processor's network. Seven IPv4 prefixes announced from Germany, no IPv6, three thousand and seventy-two addresses, across two observed BGP neighbours.
Notable
- One block's netname is two words saying it exists for internal use, while the block is publicly routed.
- Three others share a netname of the country code, a payment clearing company's initials, and a single date from the year two thousand.
- Two more are named for a card company's network with a number on the end, and are registered to a financial technology company in another country entirely.
- The last combines that card company's initials, a three-letter region covering three continents, and four more letters that expand nowhere.
- The contact lists include a hostmaster and a webmaster role under the clearing company's initials, and a role whose name ends with the words for data privacy.
- Eighteen addresses were queried for reverse DNS and none returned a name.
Interesting
- A privacy role in a registry contact list is a legal requirement showing up in an operational record. The registry wanted somebody to contact about the network; the company supplied the person responsible for what the network holds.
- Four company names across seven blocks, each from a different stage of the payments industry consolidating, is what this record is really documenting.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 7 prefixes · 3.07K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 7 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS16072- Registry name
- FDD
- Registrant
- GZS-MNT
- Abuse contact
- DataPrivacyOffice@firstdata.com
- Registered
- 1970-01-01
- Last changed
- 2018-09-04
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- FDD
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 13% valid · 2 valid, 14 with no ROA
- ROAs
- 2 authorising AS16072
- ASPA
- no ASPA record
- IRR
- 81% registered · 13 of 16 announcements 2 other origin
- Route objects
- 7 naming AS16072
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 436 networks and 1,771 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere