Skip to security report
Domain security report
xpostdmca-x.team favicon

xpostdmca-x.team

“xpostdmca-x.team | 521: Web server is down”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Server error The latest stored response was inconclusive Observed · HTTP probe
VirusTotal detections: 9/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Scam type: Generic Phishing
OTX: 16 refs Jun 15, 2026 CDN
API
Registrar
NiceNIC
Resolved IP
172.67.130.82
Registered
May 8, 2026
0 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
9 det.
OTX references
TLS Certificate
Expired or unverified dates
Let's Encrypt / E7 · Hostname coverage not recorded
Age
5 mo
Observed status
Server error 521
PhishDestroy
DestroyList
Listed

Source evidence

5 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

9 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

16 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer: Let's Encrypt / E7

Evidence Summary

Critical
VirusTotal
9/91
OTX
16 community refs

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

xpostdmca-x.team is currently classified as a high‑risk generic phishing site. The domain was registered on May 08 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and remains active as of the report date, July 12 2026. The investigation label assigns the threat type generic_phishing, indicating that the infrastructure is being used to harvest credentials or lure victims to malicious pages.

Technical resolution shows the domain resolves to 172.67.130.82, an IP owned by Cloudflare, Inc. in Canada. Both authoritative nameservers are Cloudflare‑hosted (plato.ns.cloudflare.com and ali.ns.cloudflare.com). HTTPS is served by a Let’s Encrypt certificate (edition E7), but the web server returns HTTP 521, a Cloudflare‑specific error indicating that the origin server is refusing connections. This combination of a public‑facing CDN and a refusal status is typical for transient phishing pages that are taken down or rotated frequently.

Reputation data further corroborates malicious activity. VirusTotal records six out of ninety‑five scanners flagging the domain, and the domain appears on three independent security blocklists. It is also listed in one AlienVault OTX pulse and is actively blocked by PhishDestroy, MetaMask, and SEAL. Gridinsoft assigns a trust score of zero out of one hundred, underscoring the lack of benign reputation.

Evidence points to a live phishing campaign, but the exact payload, target brand, or credential‑stealing technique remains unknown due to the HTTP 521 response and the generic page title “Loading”. Defenders should enforce network‑level blocks for the domain and its resolved IP, monitor DNS queries for the Cloudflare nameservers, and deploy TLS inspection to capture any hidden payloads should the origin become reachable. Continuous re‑evaluation of blocklist entries and periodic VirusTotal rescans are recommended to detect any changes in the domain’s behavior.

Data coverage & collection

12 · datasets with records / 19 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
9 / 91 · engine detections
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
16 · community references
External blocklists
2 · external matches
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
172.67.130.82 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / E7
Detection & evasion
Stored browser and crawler comparison
Availability history
1 · stored state changes
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 19

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLScan analysis
  • URLQuery
  • PhishStats
  • Cloudflare Radar
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Page captures
  • HTML archives
  • Page analysis
  • Observed indicators
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Source observation history
  • Lookalike relationships
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

NICENIC INTERNATIONAL GROUP CO., LIMITED · 172.67.130.82 · DNS, TLS and retained responses

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-05activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated May 8, 2026 (161d)
HTTP Status521 Error
Technical detailsProvenance & timestamps
First DetectedJun 15, 2026
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, 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.130.82
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1
  • ali.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / E7
Valid from
2026-05-05 03:40:31
Valid until
2026-08-03 03:40:30
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-05-08 11:00:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint618cd512f01f3b2fd50a344c9499aa02e2adc1a4c787993abeb3a181ff67fb9d

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

Latest Classified Outcome 2026-10-16 10:50:17 UTC

Primary outcome Unknown reason: Origin unreachable 20% confidence
Attribution mechanism: Http 5xx source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Unknown Origin unreachable Http 5xx 20% 2026-10-16 10:50:17 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-15 22:18:18 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

9 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 9 detections
alphaMountain.ai
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Webroot
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not observed No cloaking was observed in the stored scan

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

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: transient_521: raw=transient_521; http=521; via=http_proxy; server=cloudflare

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown

    origin_unreachable · http_5xx

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
xpostdmca-x.team detected and queued for full analysis
Jun 15, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 12, 2026
VirusTotal
9/91 recorded on VirusTotal
Aug 28, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
OTX Community References
16 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 3, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
DestroyList Published
Jun 15, 2026
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.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen May 8, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked 0 stored notification records Server error

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes
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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including xpostdmca-x.team)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
Read the evidence in context

About This Report: xpostdmca-x.team

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “xpostdmca-x.team | 521: Web server is down”.

VirusTotal detections for xpostdmca-x.team: 9 (2026-08-28 02:44:15 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/xpostdmca-x.team"
  title="PhishDestroy threat report for xpostdmca-x.team"
  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>