Skip to security report
Domain security and threat intelligence
ltc.metaeora.sbs favicon

ltc.metaeora.sbs

Registrar
Dynadot
Resolved IP
172.67.168.60
Registered
Apr 20, 2026
Threat verdict Critical
Availability Reachable · access restricted Reachable response; page content was not verified
VirusTotal detections: 7/92 Scam type: Impersonation Last known active
Oct 3, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 7. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
VirusTotal
7 det.
URLScan
URLScan
TLS Certificate
Expired or unverified
Age
6 mo
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed

Source evidence

6 sources

VirusTotal

7 / 92

Report

OTX

no community references

Report

URLScan capture

stored report

Stored URLScan capture preview
Report

URLScan verdict

Analysis completed

Report

CF Radar

Report stored; verdict not recorded

Report

Google Safe Browsing

Checked; no threat flag recorded

Report

Evidence Summary

Critical
VirusTotal
7/92
URLScan
Stored capture

Assessment

The domain ltc.metaeora.sbs returned an HTTP 403 status on 2026-10-06, indicating restricted server access at that time. The domain was also listed in the PhishDestroy internal catalogue on the same date.

Recorded Evidence

On 2026-10-06, an HTTP check recorded a 403 response from ltc.metaeora.sbs. The domain’s SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-06. VirusTotal checked the domain on 2026-10-05 and reported 5 detections out of 91 scanners. PageSpeed measured a performance score of 81 on 2026-10-06.

Interpretation

These dated observations show that ltc.metaeora.sbs was technically reachable by automated systems on the noted dates. The HTTP 403 response indicates server-level restrictions rather than content availability. The PhishDestroy listing and VirusTotal detections reflect security-focused scrutiny of the domain.

Recommended Actions

Retain all source records for ltc.metaeora.sbs, including HTTP, VirusTotal, PageSpeed, and PhishDestroy results. Compare new findings with these existing records to detect any changes in server responses, detection counts, or catalogue status.

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 2 captures

TLS Certificate
Certificate hostname mismatch · Issued by Let's Encrypt / YE1 · stored validity ends in 37 days

Domain details

Domain
URLScan Verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dynadot US(US)
Registration (base domain)metaeora.sbs · Created Apr 20, 2026 (170d)
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedOct 3, 2026
DOM Analysisanalyzed Oct 6, 2026score 78/100
Submitted URLhttp://ltc.metaeora.sbs/
Favicon Hash
SHORTDOT ZONE · PUBLIC EVIDENCE .sbs

ShortDot zone evidence

The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.

ShortDot SA · Luxembourg 7 zones · full-zone evidence updated daily Open the ShortDot evidence repository
ICANN OVERSIGHT Registration: metaeora.sbs

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain metaeora.sbs 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.168.60
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • kareem.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-08-16 15:36:56
Valid until
2026-11-14 15:36:55
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-05 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint476353da0041a0c9514b204d29067b244ef01d70cec4d9e9e68f9bc87181b808
Certificate names · 1 SANs
  • metaeora.sbs

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.168.60rapiddns.io

Latest Classified Outcome 2026-10-07 10:18:32 UTC

Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-10-07 10:18:32 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-07 10:18:32 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
SOCRadar
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ltc.metaeora.sbs · checked Oct 6, 2026

81
Needs Work
Performance
FCP
0.79s
First Contentful Paint
LCP
2.58s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
614ms
Total Blocking Time
SI
2.24s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. Threat First Observed 2026-10-03 19:44:34 UTC
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.168.60.

Threat Response Pipeline

Discovery
Analysis
Monitoring

7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
ltc.metaeora.sbs detected and queued for full analysis
Oct 3, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
7/92 recorded on VirusTotal
Oct 7, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 7, 2026
DestroyList Published
Oct 3, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Reachable · access restricted
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/ltc.metaeora.sbs"
  title="PhishDestroy threat report for ltc.metaeora.sbs"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>