VirusTotal
16 / 94
“Dayforce | Payroll Management Solutions”
16 / 94
5 threat-system alerts
Reportprovider verdict: malicious
Report5/14
DBL_PHISH
checked — no match recorded
11 community references
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | dayforceushcm.credit |
phishing | Phishing Block |
| Cloudflare DNS | dayforceushcm.credit |
malicious | Sinkholed |
| DigiCert UltraDNS | dayforceushcm.credit |
malicious | Sinkholed |
| Hagezi Threat Feed | dayforceushcm.credit |
malicious | Sinkholed |
| DNS4EU | dayforceushcm.credit |
malicious | Sinkholed |
The domain dayforceushcm.credit was first registered on March 07 2026 through NiceNIC International Group Co., Limited and is served by the authoritative nameservers a.dnspod.com and c.dnspod.com. Network resolution points to the IPv4 address 5.252.116.244, which belongs to ASN AS207569 operated by I‑SERVERS LTD and is geolocated in Russia. The web server terminates TLS using a Let’s Encrypt certificate (R13), indicating that encryption is enabled but the certificate is publicly issued. HTTP headers reveal the presence of Nginx as the web server and Cloudflare as a reverse‑proxy service.
Front‑end assets include Chart.js, Tailwind CSS, jQuery from the jQuery CDN, Unpkg, jsDelivr, and Tippy.js, suggesting a modern JavaScript stack typical of cloned login portals. The page title returned from the host is "Dayforce | Payroll Management Solutions," which directly references the legitimate Dayforce payroll platform, implying an attempt to masquerade as a Dayforce service. Gridinsoft’s trust‑score engine assigns a score of 0 out of 100, reflecting a severely untrusted reputation. The domain is listed on a single security blocklist and has been actively blocked by the PhishDestroy feed.
VirusTotal analysis shows that 16 of 94 scanning engines flag the domain as malicious, corroborating the blocklist findings. As of the report date the site is offline, but the infrastructure components remain active and could be re‑used. Defenders should continue to block dayforceushcm.credit at perimeter defenses, monitor DNS queries for the associated nameservers, and consider adding the IP address 5.252.116.244 to reputation‑based deny lists. Ongoing observation of the registrar NiceNIC and the hosting ASN is advised to detect any redeployment of the same infrastructure for future campaigns.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='dayforceushcm.credit', port=80): Max retries exceeded with url: / (Caused by NewConnection
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.
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.
c.dnspod.comLocation describes the IP network.
4385a16d257bea46db11b2f7887ea9321e5c616ce81953b054e1475e7ed0c09eSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of dayforceushcm.credit · checked Mar 8, 2026
19 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.
Reported by 1 community member, first seen Mar 7, 2026
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