Notification and current-status evidence
The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 5 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
bridge[.]pulsechainapp[.]com
“PulseChain Bridge - Decentralized IPFS”
साक्ष्य सारांश
bridge.pulsechainapp.com is identified as a high‑risk cryptocurrency phishing site active as of July 12 2026. The domain was created on March 12 2026 and registered through Amazon Registrar, Inc. It delivers a web page titled “PulseChain Bridge – Decentralized IPFS” that returns HTTP 200. Technical analysis shows the site is hosted on Nginx with HTTP Strict Transport Security enabled and protected by a Let’s Encrypt R13 TLS certificate. Independent scoring services assign it a Scamadviser trust score of 41 out of 100 and a Gridinsoft score of 0 out of 100, both indicating malicious behavior.
Infrastructure analysis reveals that bridge.pulsechainapp.com resolves to the public IPv4 address 35.166.104.167, which belongs to the Amazon.com, Inc. network (AS16509) and is geolocated in the United States. The domain is served by four Amazon Route 53 nameservers: ns-1381.awsdns-44.org, ns-1967.awsdns-53.co.uk, ns-487.awsdns-60.com, and an additional unnamed server. The site is currently listed on one security blocklist and has been flagged by 13 of 95 security vendors on VirusTotal, reinforcing the suspicion of phishing activity targeting users of the PulseChain ecosystem.
Defenders should prioritize blocking the IPv4 address 35.166.104.167 and the fully qualified domain name bridge.pulsechainapp.com at network perimeters and endpoint security controls. Users should be warned against visiting any site that mimics the official PulseChain bridge interface, especially those presenting the same page title and using similar branding. Continuous monitoring of the associated IP range and the Amazon‑hosted nameservers is recommended, as the threat actor may pivot to adjacent infrastructure. Incident response teams should also consider sharing indicators of compromise, such as the TLS certificate fingerprint and the observed HTTP response pattern, with threat‑sharing communities to accelerate detection across the broader security ecosystem.
भेजे गए प्रमाण का स्नैपशॉट
- भेजा गया
- लेज़र रिकॉर्ड
- 1
- केस आईडी
PD-20260312-62A40C- कैप्चर किए गए पेज का शीर्षक
- PulseChain Bridge - Decentralized IPFS
- PDF दस्तावेज़
- PDF प्रमाण
प्रमाण का पूरा पाठ
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (GB):
Computer Misuse Act 1990
Fraud Act 2006
Communications Act 2003 - Section 127
UK law criminalizes unauthorized computer access, fraud, and malicious communications.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Data Coverage
नेटवर्क सुरक्षा इंटेलिजेंस
धमकी प्रतिक्रिया पाइपलाइन
ब्लॉकलिस्ट कवरेज
10 निगरानी वाले बाहरी स्रोत · संग्रहीत स्नैपशॉट 11/08/2026
पहचान समयरेखा
-
VirusTotal
0 → 13
सहेजा गया कैप्चर
डोमेन इंटेलिजेंस
तकनीकी विवरणDNS, TLS नाम और समय-मुद्राएँ
ICANN OVERSIGHT
Registration: pulsechainapp.com
प्रत्यायन और आरएए संदर्भ
प्रत्यायन और आरएए संदर्भ
Registrar accreditation and DNS abuse obligations
For the registrable domain pulsechainapp.com behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
वायरसटोटल विश्लेषण
क्या आप इस साइट से प्रभावित हुए?
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
अपने स्थानीय अधिकारियों को रिपोर्ट करें
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।
किसी भी डोमेन की जाँच करें
संग्रहीत ब्लॉकलिस्ट, WHOIS, DNS और सार्वजनिक स्कैन साक्ष्य का उपयोग करके खतरे का विश्लेषण
अभी स्कैन करेंफ़िशिंग की रिपोर्ट करें
संदिग्ध डोमेन हमारे थ्रेट डेटाबेस में जमा करें — समुदाय की सुरक्षा करें
रिपोर्ट करेंसीधा खतरा फीड
हाल की फ़िशिंग रिपोर्टें और उपलब्धता में परिवर्तन देखे गए
निगरानी करेंजानकारी में रहें, सुरक्षित रहें
लाइव खतरों की निगरानी करें या यदि आपको लगता है कि यह एक गलत सकारात्मक है तो इस लिस्टिंग को चुनौती दें।