Skip to security report
Analytics Dashboard
Domain security report
registercard.biz favicon

registercard.biz

“Lumen Veil - Home”

Threat verdict
CriticalDomain Appeal
Assessment sources

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

Availability Unverified No conclusive current response is stored Observed · HTTP probe
Risk signals
VirusTotal detections: 6/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Across
OTX: 4 refs Aug 6, 2026 Across CDN
API
Registrar
NiceNIC
Resolved IP
172.67.187.231
Registered
Aug 3, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
This domain has been flagged as malicious
Security engines reporting a detection: 6. 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
6 det.
OTX references
4 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Expired or unverified
Age
2 mo New
PhishDestroy
DestroyList
Listed

Source evidence

8 · 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

6 / 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

4 community references

Report
Interpretation & limits

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

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

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

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

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

Evidence Summary

Critical
VirusTotal
6/91
OTX
4 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Analysis of registercard.biz shows a newly created domain that fits the profile of a malicious phishing infrastructure. The domain was registered on August 03, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and is currently resolving to the IP address 172.67.187.231, which is hosted on Cloudflare’s network as indicated by the authoritative nameservers charles.ns.cloudflare.com and gloria.ns.cloudflare.com. The domain appears on a single security blocklist and has been actively blocked by the PhishDestroy mitigation service, confirming that at least one defensive platform has identified it as abusive.

Read the full analysis2

VirusTotal records indicate that the domain was scanned by 91 independent vendors, none of which raised a detection at the time of analysis; however, the absence of detections does not constitute a safety guarantee. No public evidence such as page titles, brand references, or content snapshots has been disclosed, leaving the exact phishing lure unverified. The short lifespan of the domain, combined with its rapid appearance on a blocklist, suggests a deliberate, short‑term campaign aimed at evading reputation filters.

Defenders should treat registercard.biz as hostile and block any outbound or inbound traffic to the domain and its resolved IP. Network sensors should flag DNS queries for the domain, and email gateways should enforce URL filtering against it. Continuous monitoring of the IP address and associated Cloudflare nameservers is advised, as the infrastructure may be reused for additional malicious domains.

Data coverage & collection19 · datasets with records / 12 · 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
6 / 91 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
172.67.187.231 · 2 · nameserversCollection time not recorded
TLS certificate
Google Trust ServicesCollection time not recorded
Page captures
2 · retained captures
Page analysis
5 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
65/100 · mobile performance
Availability history
50 · stored state changes
Source observation history
3 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 12

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

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.
Blocklist records2 · external source matches

Public Blocklist Status

Domain, network & archiveNICENIC INTERNATIONAL GROUP CO., LIMITED · 172.67.187.231 · DNS, TLS and retained responses

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.
OTX tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NiceNIC RU(RU) PhishDestroy Investigation
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for registercard.biz →
RegistrationCreated Aug 3, 2026 (73d · New) — Expires Aug 2, 2027
Elapsed Since First Report 2 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 6, 2026
DOM Analysisanalyzed Aug 6, 2026score 88/1005 brand signals
Submitted URLhttp://registercard.biz/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.187.231
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • charles.ns.cloudflare.com
  • gloria.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid until
2026-11-01 00:00:00
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection source
PhishDestroy collector

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.187.231rapiddns.io

Latest Classified Outcome 2026-10-15 20:22:19 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-15 22:47:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-08-08 22:15:07 UTC last content: 2026-08-07 02:44:15 UTC current episode first observed: 2026-08-09 01:46:16 UTC observed RIP window: 2026-08-08 22:15:07 UTC → 2026-08-09 01:46:16 UTC · 3.52h midpoint estimate ≈ 2026-08-09 00:00:41 UTC · precision high · basis bounded
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.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Kaspersky
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of registercard.biz · checked Aug 6, 2026

65
Needs Work
Performance
FCP
3.56s
First Contentful Paint
LCP
8.68s
Largest Contentful Paint
CLS
0.089
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
3.93s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3.52
Estimate basis
Bounded by observations
Estimate precision
High

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

Detection & evasion checksStored browser and crawler observations
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

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='registercard.biz', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection history, report status and investigation channels

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. Domain Status Transition 2026-08-08 22:15:07 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-08-08 02:42:52 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Threat First Observed 2026-08-06 01:32:54 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.187.231.
Stored observation history53

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

    dns_inactive→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

Earlier observations 48
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  12. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  13. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  14. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  15. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  16. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  17. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  18. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  19. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  20. Availability monitor · Recorded state

    dns_inactive→Unknown

    origin_unreachable · http_5xx

  21. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  22. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  23. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  24. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  25. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  26. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  27. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  28. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  29. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  30. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  31. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  32. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  33. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  34. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  35. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  36. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  37. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  38. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  39. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  40. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  41. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  42. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  43. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  44. Availability monitor · Recorded state

    dns_inactive→Unknown

    probe_inconclusive

  45. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  46. Availability monitor · Recorded state

    Unavailable→Reachable

  47. Availability monitor · Recorded state

    Reachable→Unavailable

  48. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
registercard.biz detected and queued for full analysis
Aug 6, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 5, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Aug 6, 2026
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Aug 6, 2026
VirusTotal
6/91 recorded on VirusTotal
Aug 8, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Aug 6, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Aug 9, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 502); the cause was not independently established.
Aug 8, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Aug 6, 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Public Blocklist Status

Related infrastructureShared hosting, registrar records and related domains
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

4 evidence signal groups linked 0 reports recorded Unverified
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
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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
Embed this reportA 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/registercard.biz"
  title="PhishDestroy threat report for registercard.biz"
  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>