Skip to security report
Domain security and threat intelligence
autoconfig.no-spotify.com favicon

autoconfig.no-spotify.com

Registrar
Ultahost
Resolved IP
198.54.132.28
Registered
Oct 7, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation
VirusTotal detections: 14/92 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 1 Automated brand label: Spotify Young domain: 15 days old Google Safe Browsing: threat flag recorded
Oct 22, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 14. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 14 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

14 / 92 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

DBL_SPAM

OTX

no community references

Open report

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

Analysis

Critical
VirusTotal
14 / 92
Page captures
9

PhishDestroy threat report

Overview

PhishDestroy added autoconfig.no-spotify.com to its internal blocklist on 2026-10-22 following Google Safe Browsing’s SOCIAL_ENGINEERING alert. A request on the same day returned HTTP 200 with an XML content type; no page title was recorded.

How the scam works

The listing reflects a generic risk of deceptive pages that may mimic legitimate services to solicit user actions. Because the recorded page contained only XML and no visible content, no specific lure or mechanism can be confirmed from this observation.

Evidence

VirusTotal reported 14 detections (12 malicious, 2 suspicious) from 92 engines on 2026-10-14, retrieved 2026-10-22. Google Safe Browsing flagged the domain for SOCIAL_ENGINEERING on 2026-10-22. urlscan.io’s automated analysis tagged the URL as malicious with a score of 62 while its overall verdict remained clean; Cloudflare Radar labeled the domain as malicious phishing on 2026-10-22. The external blocklist Phishunt and PhishDestroy’s internal list both include the domain.

Infrastructure

The domain was nine days old at first observation and presented a Let’s Encrypt TLS certificate issued 2026-10-07, valid until 2027-01-05. The recorded IP was 198.54.132.28, associated with tzulo, inc. in Canada, and the server identified itself as LiteSpeed with HTTP/3 support.

What to do

Do not submit any information on this site; if you have already done so, change any reused passwords and enable multi-factor authentication where available. Defenders should block the domain and review logs for requests to autoconfig.no-spotify.com.

Collected source details

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

URLScan · 2026-10-16T22:29:00Z

Observed: · Retrieved:

Uuid
01a146d5-217d-776c-bb3e-a74ba77f8596
Final url
https://autoconfig.no-spotify.com/
Status
200
Ip
198.54.132.28
Ptr
static-198-54-132-28.cust.tzulo.com
Contacted IP addresses
[
    "198.54.132.28"
]
Asns
[
    "11878"
]
Countries
[
    "CA"
]
Document hash
bc5557d26f9090c90f85341c659bb49e82bc2fbfffaf8cc05f609da33328ba90
Tls
{
    "san": [
        "autoconfig.no-spotify.com",
        "autodiscover.no-spotify.com",
        "cpanel.no-spotify.com",
        "cpcalendars.no-spotify.com",
        "cpcontacts.no-spotify.com",
        "mail.no-spotify.com",
        "no-spotify.com",
        "webdisk.no-spotify.com",
        "webmail.no-spotify.com",
        "www.no-spotify.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "no-spotify.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-05T01:02:39Z",
    "valid_from": "2026-10-07T01:02:40Z"
}
Domain age days
9
Apex age days
9
Tls age days
9
Tls valid days
89
Requests
3
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 62,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "application/xml"
}
Cloudflare Radar · 2026-10-22T05:21:54Z

Observed: · Retrieved:

Uuid
21c9b87c-defa-4b12-94f3-20a14db2a72a
Final url
https://autoconfig.no-spotify.com/
Status
200
History
[
    {
        "url": "https://autoconfig.no-spotify.com/",
        "status": 200
    }
]
DOM structure hash
963fc2c0462153307ef60d4b812223716a0979e59f14ece9366dd6f571298589
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "autoconfig.no-spotify.com",
        "type": "A",
        "value": "198.54.132.28"
    }
]
Dnssec valid
false
Ip
198.54.132.28
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Ultahost, Inc.",
    "created": "2026-10-07T00:17:09Z",
    "updated": "2026-10-07T00:17:09Z",
    "expires": "2027-10-07T00:17:09Z",
    "nameservers": [
        "ns1.ultahost.com",
        "ns2.ultahost.com",
        "ns3.ultahost.com",
        "ns4.ultahost.com"
    ]
}
VirusTotal · 2026-10-14T19:41:21Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 12,
    "suspicious": 2,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "phishing",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Ultahost, Inc.
Created
2026-10-07T00:17:09Z
Expires
2027-10-07T00:17:09Z
Updated
2026-10-07T00:17:09Z
First seen
2026-10-07T17:41:14Z
DNS records
[
    {
        "ttl": 14400,
        "type": "A",
        "value": "198.54.132.28"
    }
]
Dns at
2026-10-14T19:46:47Z
Jarm
29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae
Certificate
{
    "san": [
        "autoconfig.no-spotify.com",
        "autodiscover.no-spotify.com",
        "cpanel.no-spotify.com",
        "cpcalendars.no-spotify.com",
        "cpcontacts.no-spotify.com",
        "mail.no-spotify.com",
        "no-spotify.com",
        "webdisk.no-spotify.com",
        "webmail.no-spotify.com",
        "www.no-spotify.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "59e4ef6e33843319505a87cf4ed5960b804",
    "sha256": "e9afe2d0afc7fb558c6711045223a84f2bd38760a4368ba5ca42a7fda92f4000",
    "subject": "no-spotify.com",
    "valid_to": "2027-01-05T01:02:39Z",
    "valid_from": "2026-10-07T01:02:40Z"
}
Registration record
{
    "registrar": "Ultahost, Inc.",
    "registrar_iana_id": "4331",
    "registrar_url": "https://ultahost.com/",
    "created": "2026-10-07T00:17:09Z",
    "updated": "2026-10-07T00:17:09Z",
    "expires": "2027-10-07T00:17:09Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "ns1.ultahost.com",
        "ns2.ultahost.com",
        "ns3.ultahost.com",
        "ns4.ultahost.com"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-22T05:25:25Z
Caa records
{
    "domain": "autoconfig.no-spotify.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-22T05:22:16Z",
    "first": "2026-10-22T05:22:16Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 962
}
Security contact file
{
    "present": true,
    "found_in": "/.well-known/security.txt"
}
Trackers
{
    "requests": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 389,
        "tls": 137,
        "wait": 169,
        "connect": 130,
        "download": 0
    },
    "response_ms": 825
}
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": [
        21,
        25,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Carbon
{
    "bytes": 874,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "149.28.254.81",
            "host": "ns4.ultahost.com"
        },
        {
            "ip": "167.71.73.238",
            "host": "ns1.ultahost.com"
        },
        {
            "ip": "94.130.75.18",
            "host": "ns3.ultahost.com"
        },
        {
            "ip": "51.38.114.43",
            "host": "ns2.ultahost.com"
        }
    ],
    "zone": "no-spotify.com"
}
Location
{
    "ip": "198.54.132.28",
    "asn": "11878",
    "org": "tzulo, inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "no-spotify.com"
}
DNS records
{
    "A": [
        "198.54.132.28"
    ]
}
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": "198.54.132.28",
    "family": 4
}
Redirects
{
    "chain": [
        "https://autoconfig.no-spotify.com"
    ]
}
Tech stack
{
    "technologies": [
        "LiteSpeed",
        "HTTP/3"
    ]
}
Registration record
{
    "registrar": "Ultahost, Inc.",
    "created": "2026-10-07T00:17:09Z",
    "updated": "2026-10-07T00:17:09Z",
    "expires": "2027-10-07T00:17:09Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.ultahost.com",
        "ns2.ultahost.com",
        "ns3.ultahost.com",
        "ns4.ultahost.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "LiteSpeed",
        "content-type": "application/xml"
    }
}
Blocklist matchesPhishDestroy · Phishunt 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Last checked

Stored Capture · 9 captures

Domain details

Domain
Google Safe Browsing Flagged Social engineering checked Oct 22, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 22, 2026
Registrar (base domain) Ultahost
Registration (base domain)no-spotify.com · Created Oct 7, 2026 (15d · Very New!) — Expires Oct 7, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 10/1001 brand signal
Submitted URLhttp://autoconfig.no-spotify.com/
Automated brand references
Spotify
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 74 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
198.54.132.28
Network ASN
AS11878
Organization
tzulo, inc.
Observed location
Toronto, CA
Server header
LiteSpeed

Nameservers 4

  • ns1.ultahost.com
  • ns2.ultahost.com
  • ns3.ultahost.com
  • ns4.ultahost.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-07 01:02:40
Valid until
2027-01-05 01:02:39
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte9afe2d0afc7fb558c6711045223a84f2bd38760a4368ba5ca42a7fda92f4000
Certificate names · 10 SANs
  • autoconfig.no-spotify.com
  • autodiscover.no-spotify.com
  • cpanel.no-spotify.com
  • cpcalendars.no-spotify.com
  • cpcontacts.no-spotify.com
  • mail.no-spotify.com
  • no-spotify.com
  • webdisk.no-spotify.com
  • webmail.no-spotify.com
  • www.no-spotify.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 14 detections
alphaMountain.ai
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
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. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    14/92 engine detections

    View source
  3. Added to PhishDestroy

    autoconfig.no-spotify.com

    View source

Check for cloaking

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

autoconfig.no-spotify.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 autoconfig.no-spotify.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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

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/autoconfig.no-spotify.com"
  title="PhishDestroy threat report for autoconfig.no-spotify.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>