The domain lonner.name was observed with an OTX pulse count of 31 on 2026-10-11, documenting its presence in external threat intelligence sources. An additional relevant fact is that lonner.name was first recorded on 2026-10-11, providing a recent timeline reference for its monitoring.
Recorded Evidence
OTX recorded 31 pulses for lonner.name on 2026-10-11, reflecting its inclusion in threat intelligence sharing. The PhishDestroy internal listing catalogued lonner.name as of 2026-10-11. The domain was first observed on 2026-10-11 and its registration date is documented as 2004-01-14 by the registrar Key-Systems GmbH.
Interpretation
The OTX source contains a measurement of how frequently lonner.name has been referenced in threat intelligence pulses, which can be used to assess its visibility in security communities. The PhishDestroy listing documents lonner.name in an internal catalogue, providing a publisher-specific reference point for monitoring. These sources together capture both external and internal detection contexts relevant to the domain as of their respective dates.
Recommended Actions
To maintain a comprehensive security profile for lonner.name, retain the OTX pulse count and PhishDestroy listing records for future comparison. Review and archive these source entries to track any changes in external intelligence or publisher-specific detection over time. Regularly consult updated records from OTX and PhishDestroy to ensure ongoing awareness of the domain’s recorded status.
DOM Analysisanalyzed 2026年10月11日score 73/1001 brand signal
Submitted URLhttp://lonner.name/
Favicon Hash
ケース ID
ページタイトル
455 Security Incident Detected
Impersonates
Wordpress
TLS証明書
Certificate hostname mismatch·
発行者 Let's Encrypt / YR2· stored validity ends in 45 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
93.191.156.190
Network ASN
AS48854
Organization
team.blue Denmark A/S
Observed location
Skanderborg, DK
Server header
Simply.com
ネームサーバー 4
ns1.simply.com
ns2.simply.com
ns3.simply.com
ns4.simply.com
Mail routing 1 MX record
mx.simply.compriority 10
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR2
Valid from
2026-08-28 06:09:56
Valid until
2026-11-26 06:09:55
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3889d2b865f46cea1c6ac0c11d08192d99e4fb7a3d57b4be1a1a550e09d3b50dCertificate names · 1 SANs
www.lonner.name
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Cloudflare Challenge85% confidence
AttributionCloudflaremechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCloudflare ChallengeCloudflareChallenge85%2026-10-11 10:03:31 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:03:31 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-10 22:03:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 93.191.156.190.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
8 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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(DE)
