VirusTotal
7 / 92 engine detections
Open report“A Smarter Sticky Note Alternative | DeskBoard Buddy”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 27 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
7 / 92 engine detections
Open report2 det.
Open reportMalicious
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added boardlyfe.shop to its internal blocklist as a suspicious domain. The recorded page title is “A Smarter Sticky Note Alternative | DeskBoard Buddy”. The domain was first observed by PhishDestroy on 2026-10-20.
Because the site is flagged without a concrete category, the exact malicious technique is unclear; the detection relies on heuristic and reputation signals rather than observed phishing, malware, or wallet‑draining behavior. No specific scam mechanism has been identified on this page.
VirusTotal scanned the domain on 2026-10-11 and reported 7 detections out of 92 engines, with AlphaMountain.ai, CRDF, G-Data, Gridinsoft, LevelBlue, Netcraft and Webroot flagging it. Google Safe Browsing checked on 2026-10-20 reported no threat. No external blocklists listed the domain as of 2026-10-20, while PhishDestroy’s own list marked it as suspicious on that date. OTX recorded three pulses mentioning the domain on 2026-10-20.
The recorded IP address for boardlyfe.shop is 37.72.142.130. A TLS certificate issued by Let’s Encrypt (YE1) was observed on 2026-10-20. No additional registration or hosting details are available.
Visitors should not enter any credentials or personal data on the site and should close the browser tab if it was opened. Organizations should add boardlyfe.shop to their deny lists, review recent access logs for connections from the recorded IP, and monitor for related indicators. If any credentials were submitted, change them immediately; otherwise, no further action is required.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a15aa6-c85d-72d8-9587-d85e4fcdbec3 |
|---|---|
| Final url | https://boardlyfe.shop/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://boardlyfe.shop/",
"from": "http://boardlyfe.shop/",
"status": 307
}
] |
| Ip | 37.72.142.130 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.250.183.35",
"142.250.195.234",
"37.72.142.130"
] |
| Asns | [
"15169",
"199242"
] |
| Countries | [
"US",
"GE"
] |
| Document hash | a662a4ef12dd2e8b0923f2b170ff0b3965e3ecd35058a9be2a45de553d70a16c |
| Script hashes | [
"66d8281fc1221b76be9090128cd41c8da92adeb9b43a15c8f16dc22ae21b5f99",
"da1c9803523e7a18f5f93419f7dbf9cab702b5a78564eb9dc0e18c32e492ae4f",
"56bef185cd5d43be7d55db75e9756858e8a4093525595194b8d3202210013efe",
"2d9ed79eb6d7a824a49129543fe8712e46fdc8f048e145692492d81f589f33b5",
"b9adf20c93dc3a7aa37cdb5f5b6d86d4252964d97a6cf3fd5ce6f143da225d82",
"acfed8ce931532ba4fbcdbc534468ab16b1e4ab08c8f8b9859558b9fbfc86d3e",
"5790cd3ddf6d13150fad9403a3be5269f8bb5c8905966746bca6929477b611e0",
"cac7c96146dad0bbe55d718c23f7af31cca28565413d9915c256932a69ae83df",
"ef598e4df04d2d336c9267057130a0ab7a499d928810f0bceb6393f28a5fcb03",
"915eca2ddd30cf0f0dcf655424d66e36e55d66a038b3365bfff815980b355c29"
] |
| Globals | [
"__next_f",
"$RC",
"webpackChunk_N_E",
"_N_E",
"next",
"_N_E_STYLE_LOAD",
"Prism"
] |
| Cookies | [
"_4iz_cid",
"_4iz_rg",
"_4iz_rid",
"_site_domain"
] |
| Storage keys | [
"analytics_session_id",
"analytics_session_id_ts",
"__analytics_utm__",
"analytics_visitor_id"
] |
| Tls | {
"san": [
"boardlyfe.shop"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "boardlyfe.shop",
"protocol": "TLS 1.3",
"valid_to": "2026-12-25T07:45:12Z",
"valid_from": "2026-09-26T07:45:13Z"
} |
| Domain age days | 144 |
| Apex age days | 144 |
| Tls age days | 24 |
| Tls valid days | 89 |
| Requests | 39 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 87,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"fakeshop"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Fake Shop"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin-when-cross-origin"
} |
Observed: · Retrieved:
| Uuid | 8a3d75f7-c49d-4e2f-a4ce-d332f5e91dca |
|---|---|
| Final url | https://boardlyfe.shop/ |
| Status | 200 |
| History | [
{
"url": "https://boardlyfe.shop/",
"status": 200
}
] |
| DOM structure hash | 09e1441965a2ff169b81d8f87fa23b5320ee7a28f7dfff932507b94ba48a2bb3 |
| Document hash | 85fccbe5172db3cc16878a52f823c744b9c9b4b6b6e741d799b7fac6ad2348df |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "boardlyfe.shop",
"type": "A",
"value": "37.72.142.130"
}
] |
| Dnssec valid | false |
| Ip | 37.72.142.130 |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 50,
"malicious": 5,
"suspicious": 2,
"undetected": 35
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"G-Data": "malware",
"Webroot": "malicious",
"Netcraft": "malicious",
"LevelBlue": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Business/Economy, Suspicious (alphaMountain.ai)"
} |
| First seen | 2026-05-29T09:58:31Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "37.72.142.130"
},
{
"ttl": 21600,
"type": "NS",
"value": "erin.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "cullen.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "cullen.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-11T11:16:08Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"boardlyfe.shop"
],
"issuer": "Let's Encrypt / YE1",
"serial": "6dd3f45bfd22baae36d40b73837c6b672d6",
"sha256": "02a0aa2918289dac1025fa466c93ca83ae46f8ee99374040fe16f4a41335536d",
"subject": "boardlyfe.shop",
"valid_to": "2026-12-25T07:45:12Z",
"valid_from": "2026-09-26T07:45:13Z"
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "boardlyfe.shop"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-10-20T18:55:39Z",
"first": "2026-10-20T18:55:39Z",
"changes": 0,
"days_archived": 1,
"avg_page_bytes": 45130
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_128_GCM_SHA256",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
22,
80,
443,
8000
]
} |
| Dns server | {
"ns": [
{
"ip": "108.162.192.113",
"host": "erin.ns.cloudflare.com"
},
{
"ip": "162.159.44.91",
"host": "cullen.ns.cloudflare.com"
}
],
"zone": "boardlyfe.shop"
} |
| Location | {
"ip": "37.72.142.130",
"asn": "199242",
"org": "Malakmadze Web LLC",
"country": "GE"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "boardlyfe.shop"
} |
| DNS records | {
"A": [
"37.72.142.130"
],
"NS": [
"cullen.ns.cloudflare.com",
"erin.ns.cloudflare.com"
],
"SOA": "{\"nsname\": \"cullen.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415820155, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Get ip | {
"ip": "37.72.142.130",
"family": 4
} |
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.
cullen.ns.cloudflare.comerin.ns.cloudflare.comLocation describes the IP network.
02a0aa2918289dac1025fa466c93ca83ae46f8ee99374040fe16f4a41335536dSaved 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 boardlyfe.shop · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://boardlyfe.shop/https://boardlyfe.shop/Cache-Control: private, no-cache, no-store, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8summary_large_imageh3=":443"; ma=2592000private, no-cache, no-store, max-age=0, must-revalidategziptext/html; charset=utf-8Tue, 20 Oct 2026 18:53:35 GMT; rel=preload; as="style"strict-origin-when-cross-originchunkedRSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable→Unavailable
Unknown→live_content
content_served
Unknown→live_content
content_served
Reachable
No threat flag
View source3 community references
View source7/92 engine detections
View sourcePD-20261020-9672A6
boardlyfe.shop
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
boardlyfe.shop
PD-20261020-9672A6 Recipient: abuse@rashost.com 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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
boardlyfe.shop)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.