Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 6/92 engines flagged. malicious: 6. suspicious: 0. Analysis time (as stored): 2026-10-31T18:54:22Z. Retrieved (as stored): 2026-11-04T18:50:49Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
menards.co.com favicon

menards.co.com

In short

PhishDestroy first recorded menards.co.com on 2026-10-31. Stored VirusTotal result: 6/92 engines flagged. malicious: 6. suspicious: 0. Analysis time (as stored): 2026-10-31T18:54:22Z. Retrieved (as stored): 2026-11-04T18:50:49Z.

“co.com”

Review the evidence
Registrar
Moniker Online Services
Resolved IP
Canada169.60.151.232SoftLayer
First observed
Oct 31, 2026
PhishDestroy assessment Critical
80/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 6/92
VirusTotal
6 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 76
Page captures
4
open gallery
Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded menards.co.com on 2026-10-31. Stored VirusTotal result: 6/92 engines flagged. malicious: 6. suspicious: 0. Analysis time (as stored): 2026-10-31T18:54:22Z. Retrieved (as stored): 2026-11-04T18:50:49Z. Risk: critical (80/100). Registrar: Moniker Online Services. Status: Last known active. Hosting: SoftLayer. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
6 / 92
Hosting
Canada169.60.151.232SoftLayer
Registrar
Moniker Online Services
Page captures
4
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for menards.co.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 6 / 92 7 sources

VirusTotal

6 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
6
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
VIPRE
malware
Fortinet
phishing
SOCRadar
phishing
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Created

Updated

First seen

DNS records

  • TTL, seconds
    14400
    Type
    MX
    Value
    lastmx.spamexperts.net
    Priority
    30
  • TTL, seconds
    3600
    Type
    CNAME
    Value
    co.com
  • TTL, seconds
    300
    Type
    A
    Value
    169.60.151.232
  • TTL, seconds
    14400
    Type
    TXT
    Value
    v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all
  • TTL, seconds
    14400
    Type
    TXT
    Value
    google-site-verification=7OcubotXUUSYYCSil8JjPJ_2uxorUHKIpmbUGsV_caA
  • TTL, seconds
    14400
    Type
    MX
    Value
    mx.spamexperts.com
    Priority
    10
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns4.nic.co.com
  • TTL, seconds
    3600
    Type
    SOA
    Responsible mailbox
    hostmaster.co.com
    Value
    ns0.nic.co.com
  • TTL, seconds
    3599
    Type
    CNAME
    Value
    co.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns1.nic.co.com
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns2.nic.co.com
  • TTL, seconds
    14400
    Type
    MX
    Value
    fallbackmx.spamexperts.eu
    Priority
    20
  • TTL, seconds
    3600
    Type
    NS
    Value
    ns3.nic.co.com

DNS records observed

JARM fingerprint

15d3fd16d29d29d00042d43d0000009ec686233a4398bea334ba5e62e34a01

Certificate

Subject alternative names
  • co.com
  • mail.co.com
  • server.co.com
  • www.server.co.com
Issuer
Let's Encrypt / YR2
Serial
625cc250a889da0d0cdc877e466a50f2379
SHA-256
d24c754ee885503c5acd67c09a18b9004fc0140c804351a910766b0f8c15dcf0
Subject
server.co.com
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 6,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "VIPRE": "malware",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Created
2026-03-07T00:00:00Z
Updated
2026-03-07T00:00:00Z
First seen
2026-03-07T21:47:07Z
DNS records
[
    {
        "ttl": 14400,
        "type": "MX",
        "value": "lastmx.spamexperts.net",
        "priority": 30
    },
    {
        "ttl": 3600,
        "type": "CNAME",
        "value": "co.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "169.60.151.232"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "google-site-verification=7OcubotXUUSYYCSil8JjPJ_2uxorUHKIpmbUGsV_caA"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "mx.spamexperts.com",
        "priority": 10
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns4.nic.co.com"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "hostmaster.co.com",
        "value": "ns0.nic.co.com"
    },
    {
        "ttl": 3599,
        "type": "CNAME",
        "value": "co.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns1.nic.co.com"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns2.nic.co.com"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "fallbackmx.spamexperts.eu",
        "priority": 20
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns3.nic.co.com"
    }
]
Dns at
2026-10-31T18:59:39Z
Jarm
15d3fd16d29d29d00042d43d0000009ec686233a4398bea334ba5e62e34a01
Certificate
{
    "san": [
        "co.com",
        "mail.co.com",
        "server.co.com",
        "www.server.co.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "625cc250a889da0d0cdc877e466a50f2379",
    "sha256": "d24c754ee885503c5acd67c09a18b9004fc0140c804351a910766b0f8c15dcf0",
    "subject": "server.co.com",
    "valid_to": "2026-12-19T14:00:48Z",
    "valid_from": "2026-09-20T14:00:49Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
6
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","DNS8","Fortinet","Gridinsoft","SOCRadar","VIPRE"]
observed_at
2026-10-31 18:54:22
checked_at
2026-11-04 19:50:55
fetched_at
2026-11-04 18:50:55
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 76

SHA-256 72619844bb4cc4e0797afc8ef554e3199bede46999f6ffd73f3cd9515605ab7e

Open report
URLScanOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Report ID

019ef8ed-49e5-771c-95fb-e9d810c868b0

Final URL

https://menards.co.com/

Redirects

  • To
    https://www.api.menards.co.com/
    From
    https://menards.co.com/
    Status
    302

Contacted domains

  • www.api.menards.co.com

Document hash

ac20ab7f12115fec751f4759f04d2d6cf8b496b5cae90bf5c062ceeef71fbd3d

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

108

Registered domain age, days

108

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
76
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
019ef8ed-49e5-771c-95fb-e9d810c868b0
Final url
https://menards.co.com/
Redirects
[
    {
        "to": "https://www.api.menards.co.com/",
        "from": "https://menards.co.com/",
        "status": 302
    }
]
Contacted domains
[
    "www.api.menards.co.com"
]
Document hash
ac20ab7f12115fec751f4759f04d2d6cf8b496b5cae90bf5c062ceeef71fbd3d
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
108
Apex age days
108
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 76,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
Separate monitor record · 2026-11-01 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
019ef8ed-49e5-771c-95fb-e9d810c868b0
score
0
malicious
false
result_at
2026-11-01T04:30:28Z
enriched_at
2026-11-01T09:16:01Z
source_timestamps
{"urlscan_result_at":"2026-11-01 05:30:28","urlscan_enriched_at":"2026-11-01 10:16:01"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 7 fields

Observed: · Retrieved:

Report ID

b400e934-b2f0-4831-bc34-5dca73939b3f

Final URL

https://menards.co.com/

Navigation history

  • URL
    https://menards.co.com/
    Status
    0

Domain risk categories

  • Business
  • Business & Economy

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    menards.co.com
    Type
    CNAME
    Value
    co.com
  • Name
    co.com
    Type
    A
    Value
    169.60.151.232
  • Name
    menards.co.com
    Type
    CNAME
    Value
    co.com

DNSSEC valid

No
Original source fields · JSON
Uuid
b400e934-b2f0-4831-bc34-5dca73939b3f
Final url
https://menards.co.com/
History
[
    {
        "url": "https://menards.co.com/",
        "status": 0
    }
]
Domain risks
[
    "Business",
    "Business & Economy"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "menards.co.com",
        "type": "CNAME",
        "value": "co.com"
    },
    {
        "name": "co.com",
        "type": "A",
        "value": "169.60.151.232"
    },
    {
        "name": "menards.co.com",
        "type": "CNAME",
        "value": "co.com"
    }
]
Dnssec valid
false

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-31T15:38:36Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-31T15:38:36Z
source_timestamp
2026-10-31 16:38:36
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 13 fields

Mail configuration

MX records
  • lastmx.spamexperts.net
  • mx.spamexperts.com
  • fallbackmx.spamexperts.eu
SPF record
v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all
SPF lookups
3

CAA records

Domain
menards.co.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
619

Trackers

Requests
1

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

DNS servers

Nameservers
  • IP address
    185.24.64.36
    Host
    ns2.nic.co.com
  • IP address
    194.169.218.36
    Host
    ns1.nic.co.com
  • IP address
    212.18.249.36
    Host
    ns4.nic.co.com
  • IP address
    212.18.248.36
    Host
    ns3.nic.co.com
DNS zone
co.com

Location

IP address
169.60.151.232
ASN
36351
Organization
SoftLayer
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YR2
Subject
server.co.com

DNS records

A
  • 169.60.151.232
MX
  • Mail server
    fallbackmx.spamexperts.eu
    Priority
    20
  • Mail server
    lastmx.spamexperts.net
    Priority
    30
  • Mail server
    mx.spamexperts.com
    Priority
    10
NS
  • ns2.nic.co.com
  • ns4.nic.co.com
  • ns1.nic.co.com
  • ns3.nic.co.com
SOA
Primary nameserver
ns0.nic.co.com
Hostmaster
hostmaster.co.com
Serial
2014429535
Refresh, seconds
900
Retry, seconds
1800
Expiry, seconds
6048000
Minimum TTL, seconds
3600
TXT
  • google-site-verification=7OcubotXUUSYYCSil8JjPJ_2uxorUHKIpmbUGsV_caA
  • v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all
CNAME
  • co.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
No

IP lookup

IP address
169.60.151.232
IP version
4
Original source fields · JSON
Mail configuration
{
    "mx": [
        "lastmx.spamexperts.net",
        "mx.spamexperts.com",
        "fallbackmx.spamexperts.eu"
    ],
    "spf": "v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all",
    "spf_lookups": 3
}
Caa records
{
    "domain": "menards.co.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T15:11:59Z",
    "first": "2026-10-31T15:11:59Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 619
}
Trackers
{
    "requests": 1
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "185.24.64.36",
            "host": "ns2.nic.co.com"
        },
        {
            "ip": "194.169.218.36",
            "host": "ns1.nic.co.com"
        },
        {
            "ip": "212.18.249.36",
            "host": "ns4.nic.co.com"
        },
        {
            "ip": "212.18.248.36",
            "host": "ns3.nic.co.com"
        }
    ],
    "zone": "co.com"
}
Location
{
    "ip": "169.60.151.232",
    "asn": "36351",
    "org": "SoftLayer",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "server.co.com"
}
DNS records
{
    "A": [
        "169.60.151.232"
    ],
    "MX": [
        "{\"exchange\": \"fallbackmx.spamexperts.eu\", \"priority\": 20}",
        "{\"exchange\": \"lastmx.spamexperts.net\", \"priority\": 30}",
        "{\"exchange\": \"mx.spamexperts.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns2.nic.co.com",
        "ns4.nic.co.com",
        "ns1.nic.co.com",
        "ns3.nic.co.com"
    ],
    "SOA": "{\"nsname\": \"ns0.nic.co.com\", \"hostmaster\": \"hostmaster.co.com\", \"serial\": 2014429535, \"refresh\": 900, \"retry\": 1800, \"expire\": 6048000, \"minttl\": 3600}",
    "TXT": [
        "google-site-verification=7OcubotXUUSYYCSil8JjPJ_2uxorUHKIpmbUGsV_caA",
        "v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60.135.222 a:codotcom.kayako.com include:servers.mcsv.net -all"
    ],
    "CNAME": [
        "co.com"
    ]
}
Dnssec
{
    "ds": true,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "169.60.151.232",
    "family": 4
}

Questions about menards.co.com

Is menards.co.com legit?

PhishDestroy rates menards.co.com as critical risk (80/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 6/92 engines flagged. malicious: 6. suspicious: 0. Analysis time (as stored): 2026-10-31T18:54:22Z. Retrieved (as stored): 2026-11-04T18:50:49Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is menards.co.com safe to connect a wallet?

This report does not record which wallet requests menards.co.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used menards.co.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 4 captures

URLScan · 2026-03-19 1 / 4
SourceURLScan · 2026-03-19
Recorded
StateStored capture
HTTP status200
Final URLhttps://menards.co.com/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 76 report ↗
IP Reputation Canada169.60.151.232 abuse score 0/100 0 reports checked Oct 31, 2026 last reported
Platform provider Moniker Online Services
Abuse contact["6008f20c01d5daacs@"]
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://menards.co.com/
Favicon Hash
Observed page title
co.com
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 44 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Canada169.60.151.232
Network ASN
AS36351
Organization
SoftLayer
Observed location
CanadaToronto, CA
Server header
Apache

Nameservers 4

  • ns2.nic.co.com
  • ns4.nic.co.com
  • ns1.nic.co.com
  • ns3.nic.co.com

SOA

  • nsname: ns0.nic.co.com
  • hostmaster: hostmaster.co.com
  • serial: 2014429535
  • refresh: 900
  • retry: 1800
  • expire: 6048000
  • minttl: 3600

Mail routing 3 MX records

  • fallbackmx.spamexperts.eupriority 20
  • lastmx.spamexperts.netpriority 30
  • mx.spamexperts.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-20 14:00:49
Valid until
2026-12-19 14:00:48
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd24c754ee885503c5acd67c09a18b9004fc0140c804351a910766b0f8c15dcf0
Certificate names · 4 SANs
  • co.com
  • mail.co.com
  • server.co.com
  • www.server.co.com

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

viewdns.info · 169.60.151.232rapiddns.io

Latest Classified Outcome 2026-11-05 02:31:21 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-05 02:31:21 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 02:31:21 UTC last content: 2026-11-05 02:31:21 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.menards.co.comDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 6 detections
DNS8
VIPRE
Fortinet
SOCRadar
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://menards.co.com/
co.com
Response
HTTP 200
HTML body
255 B
Compressed
182 B
Links
0 internal · 1 external
Detected technologies
apache
Selected response headers
Server: Apache
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Saved response-header values · 8
Accept-Ranges
bytes
Connection
Keep-Alive
Content-Length
255
Content-Type
text/html
Date
Sat, 31 Oct 2026 15:15:03 GMT
Keep-Alive
timeout=5, max=100
Last-Modified
Fri, 15 May 2026 04:56:56 GMT
Server
Apache

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 6 SHA-256 hashes: 4 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 15:22 UTC.

Open this scan on URLScan 019ef8ed-49e5-771c-95fb-e9d810c868b0 ↗

Stored observation history6

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

    live_content

    content_served

  2. VirusTotal · Detection count

    5→6

    Engines added
    VIPRE
    Engines removed
    None recorded
    Recorded vendor total
    6
  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 1
  1. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations19

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:21.000000
    Evidence SHA-256
    d3e2509a24071621cc5a843714e5ab7a5faa4a06b7cce872965378d0819b96fe
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:31:21
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:31:21.000000
    Evidence SHA-256
    d3e2509a24071621cc5a843714e5ab7a5faa4a06b7cce872965378d0819b96fe
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:31:21
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:31.000000
    Evidence SHA-256
    1714cdf976ccefc3d963e63fab11ac489bd52e771da914d26b506f41b7d67cb0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:31
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:07:31.000000
    Evidence SHA-256
    1714cdf976ccefc3d963e63fab11ac489bd52e771da914d26b506f41b7d67cb0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:07:31
    Evidence reason
    alive_content
  6. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  7. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  8. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:00:55.000000
    Evidence SHA-256
    70101cb439ee5475c0e6fe8dcb93f68909747ef148da801a69b0b40c230e306d
    Evidence timestamp as recorded
    2026-11-02 12:00:55
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:00:55.000000
    Evidence SHA-256
    c4aa4c97cf0902ec984b0e6ae0ed6f9c7c1c4a8c060d2894bc42d4516d219393
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:00:55
    Evidence reason
    alive_content
  10. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:45.000000
    Evidence SHA-256
    d6db718d16b81badf61b903296531273fd72f070a9dffe358c11e61218989fad
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:45
    Evidence reason
    alive_content
  11. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:02:45.000000
    Evidence SHA-256
    d6db718d16b81badf61b903296531273fd72f070a9dffe358c11e61218989fad
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:45
    Evidence reason
    alive_content
  12. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 23:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:03:04.000000
    Evidence SHA-256
    f11482c658fb887f1ce106f6106ba0fc70eb26e4cabfb74a33a3611e68f7b099
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:03:04
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:03:04.000000
    Evidence SHA-256
    f11482c658fb887f1ce106f6106ba0fc70eb26e4cabfb74a33a3611e68f7b099
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:03:04
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:45:33.000000
    Evidence SHA-256
    bd2bf5383294fc64f6a080d8cb55b8c171e97384fa3647b1f1bfcd5a4ed859bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:45:33
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:45:33.000000
    Evidence SHA-256
    bd2bf5383294fc64f6a080d8cb55b8c171e97384fa3647b1f1bfcd5a4ed859bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:45:33
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:00:19.000000
    Evidence SHA-256
    61084088f5552e7d5973743b1c205c67af954a82a4dfa4ab50c430244fafef39
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:00:19
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:00:19.000000
    Evidence SHA-256
    61084088f5552e7d5973743b1c205c67af954a82a4dfa4ab50c430244fafef39
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:00:19
    Evidence reason
    alive_content
  19. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 16:23:15.282508
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    menards.co.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 76
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 6/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (5 → 6): VIPRE
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. VirusTotal

    6/92 engine detections

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    menards.co.com

    View source
  4. URLScan

    Malicious · engine verdict · score 76

    View source
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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

menards.co.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report 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
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 menards.co.com)
  • 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

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

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 →
About this reportSources, observation dates and corrections

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.

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.

Request a correction or appeal How PhishDestroy works
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/menards.co.com"
  title="PhishDestroy threat report for menards.co.com"
  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>