Spamhaus DBL
DBL_SPAM
On 2026-10-05, starlockerfort.com was listed in the PhishDestroy internal catalogue, and OTX recorded activity for the domain on the same date. The domain was also registered recently, which is reflected in its evidence timeline.
PhishDestroy internally listed starlockerfort.com on 2026-10-05. OTX recorded 4 pulses for the domain on 2026-10-05. The domain was registered with Dominet (HK) Limited on 2026-09-03, and its SSL certificate was issued by Let's Encrypt / YE2, with scanning recorded on 2026-10-05.
The evidence shows that starlockerfort.com appeared in both PhishDestroy and OTX records on the same day, indicating that multiple sources noted the domain's presence or activity. The registration and SSL certificate details provide additional context for its timeline and technical configuration.
Review the PhishDestroy listing and OTX pulse records for starlockerfort.com to inform any follow-up. Preserve these source records for future comparison with new observations. Track any changes in the domain’s registration or certificate information using the recorded evidence.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
79c482422a0a86048aec7e298b444d5ca10127d481653d63d7fcec5229ffa091Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
46.29.26.38. 7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive