As33514

To M247’s credit, they have a publicly documented Abuse Contact (abuse@m247.ro) and a published abuse handling policy. They are a member of the RIPE Anti-Abuse Working Group. However, the effectiveness varies:

What does the future hold for M247 Ltd and AS33514? as33514

Use whois -h whois.ripe.net AS33514 to get the official registration. For route origin validation, check the RPKI (Resource Public Key Infrastructure) status. M247 has partially deployed RPKI, but not all prefixes are cryptographically signed. Expect about 60-70% coverage for their IPv4 space. To M247’s credit, they have a publicly documented

Traffic and DNS analysis indicate that AS33514 hosts infrastructure for: As of this writing, AS33514 is not listed

If you operate a firewall, do not blanket-block AS33514; you will block legitimate hosting customers. Instead, use reputation-based blocking (e.g., feed from AbuseIPDB or VirusTotal) and monitor traffic from their known “abuse-heavy” prefixes like:

As of this writing, AS33514 is not listed on the Spamhaus “Drop” list (which would indicate a completely rogue network), but it does appear in the Spamhaus “Blocklist” (SBL) for specific subnets on a rotating basis. Network operators often rate-limit or block entire M247 ranges due to historical abuse.

| Community | Action | |-----------|--------| | 33514:100 | Prepend once to all upstreams | | 33514:200 | Do not advertise to peer X | | 33514:666 | Blackhole traffic (DDoS mitigation) |