IP abuse report2a00:1110:101:6c3e:d579:2a42:8da0:72b2

Low Risk Residential IPv6 Hungary AS5483

2a00:1110:101:6c3e:d579:2a42:8da0:72b2 is an IPv6 address located in Székesfehérvár, Hungary. It belongs to a network operated by Magyar Telekom Plc. (AS5483). The address is not listed by any of the threat-intelligence sources we track. No community reports have been filed for it yet.

Last updated Listing sources 0 Community Reports 0 How the score works
Listing sources0
Community Reports0
Distinct Reporters0
Last seen —

IP Information

ISP / Organization
Magyar Telekom Plc.
ASN
AS5483 MAGYAR-TELEKOM-MAIN-AS
ASN Domain
telekom.hu
IP Range
2a00::/11
Regional Registry
RIPENCC
Connection Type
Residential
Country
Hungary (HU)
Region / State
Fejér
City
Székesfehérvár
Time Zone
Unknown
Abuse contact
abuse@ripe.net The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Székesfehérvár Fejér, Hungary
Coordinates
47.19, 18.41
Network
AS5483 Magyar Telekom Plc.
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

No feed or community activity in the last 30 days.

Blacklist Matches

0

No matches found in any threat intelligence source.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

2

This address is not currently listed by any of our sources. The history below shows when it was.

Removed from the pool
10 days ago · score at the time: 60/100 · carried by 1 sources
2026-11-10 02:52
Added to the pool
12 days ago
2026-11-07 12:22

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 2a00:1110:101:6c3e:d579:2a42:8da0:72b2

Is 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 safe?

2a00:1110:101:6c3e:d579:2a42:8da0:72b2 scores 35/100: weak or single-source signals. Treat it as low risk and keep logging rather than blocking on this alone.

Who owns 2a00:1110:101:6c3e:d579:2a42:8da0:72b2?

2a00:1110:101:6c3e:d579:2a42:8da0:72b2 is announced by AS5483 and operated by Magyar Telekom Plc.. It sits in the 2a00::/11 block registered with RIPENCC.

Where is 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 located?

Geolocation places 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 in Székesfehérvár, Hungary. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 on a blacklist?

No. 2a00:1110:101:6c3e:d579:2a42:8da0:72b2 is not on any of the threat sources we track right now.

How do I report abuse from 2a00:1110:101:6c3e:d579:2a42:8da0:72b2?

Send your log lines to the network's abuse contact, abuse@ripe.net, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/2a00:1110:101:6c3e:d579:2a42:8da0:72b2

Guides for this IP