Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
authmy.co favicon

authmy.co

In short

PhishDestroy records the authmy.co page showing an expired sign-in link under the heading "Authentication service".

“Authentication service”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Germany207.180.58.39Dominic Scholz trading as ITP-Solutions GmbH & Co. KG
Registered
Sep 17, 2026
First observed
Nov 1, 2026
PhishDestroy assessment High
63/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 1/92
VirusTotal
1 / 92
engine detections ·
OTX
6
community references
URLScan
Malicious
engine verdict · score 57
Page captures
7
open gallery
Domain age
44 days
registered 2026-09-17 according to WHOIS
OTX: 6 refs Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the authmy.co page showing an expired sign-in link under the heading "Authentication service".

High
Status
Last known active
VirusTotal
1 / 92
Hosting
Germany207.180.58.39Dominic Scholz trading as ITP-Solutions GmbH & Co. KG
Registrar
United StatesDynadot
Registered
Sep 17, 2026
OTX
6 community refs
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured authmy.co page presents itself as an "Authentication service" and displays a single centered notice titled "Sign-in link expired." The message tells the visitor to go back to the site they were signing in to and start again — it takes a second — so the only interaction offered is returning to a prior site rather than entering credentials on this page. No other controls, forms or branding appear in the capture.

The stored VirusTotal domain result reports 1 detection out of 92 engines. SOCRadar reported "malicious".

Source evidenceVirusTotal 1 / 92 · OTX 6 references 8 sources

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
1
Suspicious
0
Undetected
36

Vendor labels

SOCRadar
malicious

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    sierra.ns.cloudflare.com
  • TTL, seconds
    60
    Type
    A
    Value
    207.180.58.39
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    bradley.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    bradley.ns.cloudflare.com

DNS records observed

JARM fingerprint

1dd40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5

Certificate

Subject alternative names
  • authmy.co
Issuer
Let's Encrypt / YE1
Serial
6e5c429add106af8a2cc9341f00e4dd4e79
SHA-256
c9056f44d5fc7d0027668605c72f4087d51b37aa5fd7e6c6c7d6623bbad9e7af
Subject
authmy.co
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
https://www.dynadot.com/
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • serverTransferProhibited
Nameservers
  • bradley.ns.cloudflare.com
  • sierra.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "SOCRadar": "malicious"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-09-17T19:24:48Z
Expires
2027-09-17T23:59:59Z
Updated
2026-09-22T19:27:12Z
First seen
2026-09-18T04:44:27Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sierra.ns.cloudflare.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "207.180.58.39"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "bradley.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "bradley.ns.cloudflare.com"
    }
]
Dns at
2026-10-30T11:57:02Z
Jarm
1dd40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5
Certificate
{
    "san": [
        "authmy.co"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6e5c429add106af8a2cc9341f00e4dd4e79",
    "sha256": "c9056f44d5fc7d0027668605c72f4087d51b37aa5fd7e6c6c7d6623bbad9e7af",
    "subject": "authmy.co",
    "valid_to": "2026-12-17T03:24:02Z",
    "valid_from": "2026-09-18T03:24:03Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "https://www.dynadot.com/",
    "created": "2026-09-17T19:24:48Z",
    "updated": "2026-09-22T19:27:12Z",
    "expires": "2027-09-17T23:59:59Z",
    "status": [
        "clientTransferProhibited",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "bradley.ns.cloudflare.com",
        "sierra.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 1 malicious + 0 suspicious / 92 · 2026-10-30 11:51:33 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-30T11:51:33Z
fetched_at
2026-11-01T02:51:37Z
stats
{"timeout":0,"harmless":55,"malicious":1,"suspicious":0,"undetected":36}

URLScan

Malicious · engine verdict · score 57

SHA-256 d9331d649cc33cc431a69c1a3aa125d43a629cc7622a2c8476c4cdf26b52fc27

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a194ea-47a7-7749-a806-41771926c40c

Final URL

https://authmy.co/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://authmy.co/
    From
    http://authmy.co/
    Status
    307

IP address

207.180.58.39

Contacted IP addresses

  • 207.180.58.39

Autonomous systems (ASN)

  • 213250

Server countries

  • DE

Document hash

d9331d649cc33cc431a69c1a3aa125d43a629cc7622a2c8476c4cdf26b52fc27

TLS session and certificate

Subject alternative names
  • authmy.co
Cipher
AES_128_GCM
Issuer
YE1
Subject
authmy.co
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

43

Registered domain age, days

43

Certificate age, days

43

Certificate validity, days

89

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
57
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx
Content-type
text/html
Original source fields · JSON
Uuid
01a194ea-47a7-7749-a806-41771926c40c
Final url
https://authmy.co/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://authmy.co/",
        "from": "http://authmy.co/",
        "status": 307
    }
]
Ip
207.180.58.39
Contacted IP addresses
[
    "207.180.58.39"
]
Asns
[
    "213250"
]
Countries
[
    "DE"
]
Document hash
d9331d649cc33cc431a69c1a3aa125d43a629cc7622a2c8476c4cdf26b52fc27
Tls
{
    "san": [
        "authmy.co"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "authmy.co",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-17T03:24:02Z",
    "valid_from": "2026-09-18T03:24:03Z"
}
Domain age days
43
Apex age days
43
Tls age days
43
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 57,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a194ea-47a7-7749-a806-41771926c40c
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

6 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

ee8b7c8f-0027-4beb-b450-cbd0e82c6eb4

Final URL

https://authmy.co/

HTTP response

200

Navigation history

  • URL
    https://authmy.co/
    Status
    200

DOM structure hash

abb8a7ff10ca0a5424ad536bb9b4e2b0e7d678043bb4180a6bf4c30105433c99

Document hash

d9331d649cc33cc431a69c1a3aa125d43a629cc7622a2c8476c4cdf26b52fc27

Domain risk categories

  • Login Screens
  • Miscellaneous

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    authmy.co
    Type
    A
    Value
    207.180.58.39

DNSSEC valid

No

IP address

127.0.1.16

127.0.1.16 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Original source fields · JSON
Uuid
ee8b7c8f-0027-4beb-b450-cbd0e82c6eb4
Final url
https://authmy.co/
Status
200
History
[
    {
        "url": "https://authmy.co/",
        "status": 200
    }
]
DOM structure hash
abb8a7ff10ca0a5424ad536bb9b4e2b0e7d678043bb4180a6bf4c30105433c99
Document hash
d9331d649cc33cc431a69c1a3aa125d43a629cc7622a2c8476c4cdf26b52fc27
Domain risks
[
    "Login Screens",
    "Miscellaneous"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "authmy.co",
        "type": "A",
        "value": "207.180.58.39"
    }
]
Dnssec valid
false
Ip
127.0.1.16

127.0.1.16 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

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-11-01T02:53:29Z

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-11-01T02:53:29Z
source_timestamp
2026-11-01 03:53:29
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
authmy.co — Sign-in link expired on Authentication service
ai_description
PhishDestroy records the authmy.co page showing an expired sign-in link under the heading "Authentication service".
ai_summary
The captured authmy.co page presents itself as an "Authentication service" and displays a single centered notice titled "Sign-in link expired." The message tells the visitor to go back to the site they were signing in to and start again — it takes a second — so the only interaction offered is returning to a prior site rather than entering credentials on this page. No other controls, forms or branding appear in the capture. The stored VirusTotal domain result reports 1 detection out of 92 engines. SOCRadar reported "malicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 03:52:40
revision
982e07c648ee5ca6114abf9b51e917237b9c6fa005d202512033ede27ebf7ac9
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
authmy.co

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.02
Average page size, bytes
935

Page title and metadata

Page title
Authentication service
Indexing directives
noindex, nofollow

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
3
TLS
19
Waiting
17
Connection
21
Download
0
Response time, ms
60

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
1182
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    162.159.44.35
    Host
    bradley.ns.cloudflare.com
  • IP address
    172.64.34.245
    Host
    sierra.ns.cloudflare.com
DNS zone
authmy.co

Location

IP address
207.180.58.39
ASN
213250
Organization
Dominic Scholz trading as ITP-Solutions GmbH & Co. KG
City
Limburg an der Lahn
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
authmy.co

DNS records

A
  • 207.180.58.39
NS
  • sierra.ns.cloudflare.com
  • bradley.ns.cloudflare.com
SOA
Primary nameserver
bradley.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418223428
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
207.180.58.39
IP version
4

Redirects

Redirect chain
  • https://authmy.co

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • serverTransferProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • bradley.ns.cloudflare.com
  • sierra.ns.cloudflare.com

HTTP headers

Response headers
Server
nginx
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "authmy.co"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-01T02:16:43Z",
    "first": "2026-09-18T12:19:27Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.02,
    "avg_page_bytes": 935
}
Page title and metadata
{
    "title": "Authentication service",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 19,
        "wait": 17,
        "connect": 21,
        "download": 0
    },
    "response_ms": 60
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 1182,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.35",
            "host": "bradley.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.245",
            "host": "sierra.ns.cloudflare.com"
        }
    ],
    "zone": "authmy.co"
}
Location
{
    "ip": "207.180.58.39",
    "asn": "213250",
    "org": "Dominic Scholz trading as ITP-Solutions GmbH & Co. KG",
    "city": "Limburg an der Lahn",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "authmy.co"
}
DNS records
{
    "A": [
        "207.180.58.39"
    ],
    "NS": [
        "sierra.ns.cloudflare.com",
        "bradley.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"bradley.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418223428, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "207.180.58.39",
    "family": 4
}
Redirects
{
    "chain": [
        "https://authmy.co"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-09-17T19:24:48Z",
    "updated": "2026-09-22T19:27:12Z",
    "expires": "2027-09-17T23:59:59Z",
    "status": [
        "serverTransferProhibited https://icann.org/epp",
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "bradley.ns.cloudflare.com",
        "sierra.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html"
    }
}

Questions about authmy.co

Is authmy.co legit?

PhishDestroy records the authmy.co page showing an expired sign-in link under the heading "Authentication service".

Is authmy.co safe to connect a wallet?

This report does not record which wallet requests authmy.co 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 authmy.co?

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

URLScan · 2026-11-01 1 / 7 Used in the analysis Source file SHA-256: e82067b34781ff16dbf1c387e57e5f89763423ceb6b005c3e78342d82a9e6df4 SHA-256 of the prepared copy given to the model: 552a4c7c031d6acf7777d96138332d9b75bfc6f9d76edadac7eeca4a6f41b8e2
SourceURLScan · 2026-11-01
Recorded
StateStored capture
Final URLhttps://authmy.co/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
IP Reputation Germany207.180.58.39 abuse score 0/100 0 reports checked Nov 1, 2026
OTX tags 2026-11affiliate fraudai-assisted scamsall-domainsatlascoreblocklistcryptocryptocurrency frauddomainsdrainerfraudlivemagnetic teammonthly+6 more
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for authmy.co →
RegistrationCreated Sep 17, 2026 (44d · New) — Expires Sep 17, 2027
Registrantf651612a2f356ad3s@ VirusTotal WHOIS
WHOIS statusserverTransferProhibitedclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://authmy.co/
Favicon Hash
Observed page title
Authentication service
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany207.180.58.39
Network ASN
AS213250
Organization
Dominic Scholz trading as ITP-Solutions GmbH & Co. KG
Observed location
GermanyLimburg an der Lahn, DE
Server header
nginx

Nameservers 2

  • bradley.ns.cloudflare.com
  • sierra.ns.cloudflare.com

SOA

  • nsname: bradley.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418223428
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-18 03:24:03
Valid until
2026-12-17 03:24:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc9056f44d5fc7d0027668605c72f4087d51b37aa5fd7e6c6c7d6623bbad9e7af
Certificate names · 1 SAN
  • authmy.co

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

viewdns.info · 207.180.58.39rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 1 detection
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of authmy.co · checked Nov 1, 2026

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.85 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://authmy.co/
Final URL: https://authmy.co/
Authentication service
Response
HTTP 200
HTML body
1.2 KB
Compressed
688 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sun, 01 Nov 2026 02:16:48 GMT
Etag
W/"6ab00239-49e"
Last-Modified
Sun, 20 Sep 2026 15:56:41 GMT
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
X-Robots-Tag
noindex, nofollow

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

Archived

Captured network requests

Network requests: 2 SHA-256 hashes: 2 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-11-01 02:24 UTC.

Open this scan on URLScan 01a194ea-47a7-7749-a806-41771926c40c ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations1

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_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-11-01 03:21:07.227521
    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
    authmy.co detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded 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: 57
  • 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: 1/92
  • OTX Community References
    Community publication references on AlienVault OTX: 6. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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

5 entries
  1. AlienVault OTX

    6 community references

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    authmy.co

    View source
  5. VirusTotal

    1/92 engine detections

    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

Check for cloaking

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

authmy.co

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 1 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 6 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
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?

4 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 authmy.co)
  • 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.

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.

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/authmy.co"
  title="PhishDestroy threat report for authmy.co"
  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>