Sh4mefulIP Address: 113.28.172.56
This page shows DMARC authentication failure data for this IP address. Learn more about this data.
Geolocation Information
- Country:
- HK Hong Kong
- Coordinates:
- 22.2578, 114.1657
WHOIS Information
- Network Name:
- FXCREATION-HK
- CIDR:
113.28.160.0/19- Owner:
- PCCW IMSBiz route object
- Reverse DNS:
-
113-28-172-56.static.imsbiz.com
Last updated: 5/18/2026
Analysis
This IP was observed generating a single DMARC authentication failure on May 17, 2026. With only one data point, the event is better read as a single suspicious observation than a sustained campaign. Every message observed from this source failed both SPF and DKIM verification. Receiving mail providers applied a reject disposition, refusing delivery outright.
The reverse DNS record (113-28-172-56.static.imsbiz.com) matches a generic ISP address pattern, typical of consumer or small-business connections rather than dedicated mail infrastructure. Mail originating from addresses like this is frequently associated with compromised endpoints, such as home routers, IoT devices, or infected personal computers being used as part of a botnet.
Geolocation places the host in Hong Kong, on infrastructure operated by PCCW IMSBiz route object. Abuse-reporting channels in this jurisdiction are generally responsive, and reports to the network operator can result in timely remediation.
The address is registered to PCCW IMSBiz route object (FXCREATION-HK). Enterprise-registered addresses that appear in DMARC failure data are typically either compromised hosts on the organization's network or outbound mail relays that are not properly authorized in the domain's SPF record.
Across the wider FXCREATION-HK network, 1 distinct IP has been associated with 1 authentication failures over 1 observed messages, spanning 1 country. Activity on this network is sparse in this dataset, suggesting isolated rather than systematic abuse.
If your domain appears in the From header of mail from this address, treat it as probable spoofing. Verify that your SPF record does not authorize this host, directly or through nested include mechanisms, and that no DKIM selector you publish has been issued to it. If both checks come back clean, the receiver's reject action is doing its job.
Your DMARC policy posture matters more than any IP-level response here. The enforcement action applied to this mail indicates your policy is already providing protection. Maintaining p=reject across all your domains closes the gap for attackers who manage partial alignment. Domains that remain at p=none long-term tend to be impersonated repeatedly, because the cost to the attacker of attempting is effectively zero.
Blocking this individual address has limited durability: an attacker can rotate to another address in the same /24 subnet at effectively zero cost. More durable responses include monitoring aggregate DMARC reports so new sources are visible as they emerge, tightening SPF to remove overly permissive include chains or +all mechanisms, and ensuring DKIM is signing every legitimate outbound stream so alignment failures are unambiguous. The formal abuse contact for PCCW IMSBiz route object is listed in APNIC WHOIS records, and timely remediation is achievable through that channel.
External Reputation Lookups
Look up this IP in external threat intelligence and reputation databases (opens in new tab):