Website reputation report

come.to

Last checked 4 hours ago · Point-in-time assessment

! Threat indicators detected

What is this website?

Public pages were observed on come.to, but their subject was not confidently classified. An About page was also found. The sampled pages were marked as English-language. Recurring page-metadata topics include links social media, plan, content into one.

Local threat indicators foundA local signature or phishing feed matched. Review the source and scope below before visiting.

63/100Safety Score
75%Evidence Confidence
Trust Radar evidence profile Eight evidence dimensions from zero to one hundred. Exact values surround the chart. Threat Intelligence25 Domain History75 Infrastructure91 Website Security95 Security Hygiene50 Transparency55 Reputation50 Operational Stability85
Trust RadarEight observed factors. Select one to inspect its evidence.

How to read this report

Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.

No automated scan can guarantee that a website is safe.

Independent evidence brief

What we observed about come.to

Updated Oct 1, 2026

The latest scan examined 0 public pages on come.to. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.

Purpose and visible content

On its About page, the site says: Welcome.to is a modern link-in-bio platform for creators and businesses. Share all your links, social media, and content in one stunning profile page.

Observed page title: Welcome.to - One Link for Everything You Share.

Registrar and domain history

Registered on Jul 7, 2024. Registrar: NAMECHEAP.

Recorded expiry date: Sep 19, 2028. Registry data can change.

Connection and hosting evidence

The checked homepage returned HTTP 200 in about 1000 ms.

A valid TLS certificate was observed, expiring Dec 7, 2026.

Threat checks and score context

External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.

Safety Score: 63/100. Evidence Confidence: 75%. These measure different things.

Public page evidence

Topics and keywords observed on come.to

12 phrases

These phrases were extracted locally from sampled public page metadata. They are observations, not search-volume or ranking estimates.

links social mediaMeta description6 sampled pages
planTitle, H1, Meta description3 sampled pages
content into oneMeta description5 sampled pages
gather allMeta description5 sampled pages
important linksMeta description5 sampled pages
one beautifulMeta description5 sampled pages
professional profileMeta description5 sampled pages
workflowTitle, H1, Meta description2 sampled pages
free planTitle, H1, Meta description2 sampled pages
pro planTitle, H1, Meta description2 sampled pages
linkTitle, H1, Meta description3 sampled pages
shareTitle, H1, Meta description3 sampled pages

At a glance

Key findings

✓

Report is current

The displayed evidence comes from the published immutable scan.

i

Confidence is separate

Unavailable evidence is shown as missing and never counted as clean.

!

Verify before sensitive actions

Check the exact URL and context before payments, credentials, or downloads.

Fully explainable

Why this score?

Versioned weights
Threat IntelligenceWeight 25%
25/100

A local antivirus signature or exact-host phishing feed match needs review. This is not proof that the entire website is compromised.

Domain HistoryWeight 10%
75/100

Domain registration age and expiry were checked.

InfrastructureWeight 10%
91/100

Observed DNS records and network address were checked.

Website SecurityWeight 15%
95/100

Observed certificate validity and TLS protocol were checked.

Security HygieneWeight 15%
50/100

Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.

TransparencyWeight 5%
55/100

Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.

ReputationWeight 5%
50/100

Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.

Operational StabilityWeight 15%
85/100

Observed HTTP status and final connection scheme were checked.

Server-side analysis

Automated security checks

Local antivirus and phishing checks

ClamAV · homepage HTMLNo signature match in the sampled HTML
Engine version1.5.4
Signature database date (UTC)2026-10-01T06:24:38+00:00
HTML bytes submitted279,857
Phishing.Database · exact hostnameHost appears in the phishing feed
Feed downloaded (UTC)2026-10-01T18:00:08+00:00
Hosts in local snapshot386,078

Sampled scripts and pages

Resource analysis incomplete

5 resources checked · 3 script links observed on the homepage. Partial resource coverage.

ClamAV inspects the fetched homepage HTML on our server. New scans also sample up to four linked scripts and two collected internal pages, with size and time limits. Scripts are not executed. Other downloads, private server files and logged-in pages remain outside this check. A signature match needs investigation and can be a false positive. No match is not a whole-site safety guarantee.

Exact hostname lookup uses a downloaded Phishing.Database snapshot. It does not send this domain to an external lookup API or mark sibling subdomains as harmful. Not listed does not mean safe. Snapshot age is download age, not proof that every entry was recently revalidated.

Homepage HTML only · Eight local rule families · local-security-v2

Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.

Page resource inventory

Linked scripts3
Inline scripts4
Embedded frames1
External script hosts1

Counts describe the sampled HTML, not every resource loaded by the browser. External resources are common and are not automatically harmful.

No listed local patterns observed. The limited rule set cannot detect every threat or behavior.

External threat intelligence

Provider coverageNot checked

Local checks do not query external reputation databases. An unavailable check is never a clean result.

Registration

Domain information

Public RDAP observation
Canonical domaincome.to
RegistrarNAMECHEAP
RegisteredJul 7, 2024
Domain age2 years
ExpiresSep 19, 2028
Registry statusesactive
Report statePublished

Infrastructure

Network & hosting

Observed endpoint, not legal location
IP address188.114.96.2
Autonomous systemUnavailable
Network organizationUnavailable
Observed countryUnavailable
CDNCloudflare
Web application firewallNot detected

At a glance

Infrastructure summary

Observed during this scan

A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.

HTTP response200 · https://welcome.to/
Endpoint188.114.96.2
NetworkUnavailable
CDN and WAFCloudflare · Not detected
DNS surface8 records · 2 nameservers · 1 mail exchangers
Protection signals1 security headers · 4 technologies · DNSSEC unknown

Page telemetry

Observed page statistics

Safe metadata only

These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.

Response size279,857 bytes
HTTP check duration1,000 ms
Cookies observed2
Script resources3 · 1 external hosts
Frames and sampled checks1 frames · 5 resources checked

Encrypted transport

TLS certificate

Valid when observed
StatusValid when observed
ProtocolTLSv1.3
IssuercountryName=US, organizationName=Google Trust Services, commonName=WE1
Valid fromSep 8, 2026
Valid untilDec 7, 2026
Certificate names*.come.to · come.to

Resolution

DNS footprint

DNSKEY status unknown

DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.

A188.114.96.2TTL —
A188.114.97.2TTL —
AAAA2a06:98c1:3120::2TTL —
AAAA2a06:98c1:3121::2TTL —
NSchin.ns.cloudflare.comTTL —
NSvick.ns.cloudflare.comTTL —
MX0 mail.come.toTTL —
TXTv=spf1 +a +mx +ip4:103.227.176.15 +ip4:195.85.19.67 include:spf.supercp.com include:mxsspf.sendpulse.com ~allTTL —

DNS observations · no external lookup API

Domain email protection

Exact-host SPF and DMARC observations help the owner investigate email impersonation risks. They are separate from website malware checks and do not change the Safety Score.

SPFPolicy record observed, not fully validated
DMARCMonitoring-only DMARC policy

What to do next

Review the records with your mail administrator. Inventory legitimate senders and test SPF and DKIM alignment before enforcing a stricter DMARC policy. Fix duplicate records and investigate overly permissive SPF rules.

This bounded check does not send email, probe SMTP, evaluate recursive SPF includes, verify DKIM signatures or apply organizational-domain DMARC inheritance. A missing subdomain record does not prove that no inherited protection exists. A DNS timeout is unknown, not an absent record. A policy record is not proof that messages authenticate successfully.

Responsible disclosure

security.txt

RFC 9116 observation

No readable security.txt file was observed at the standard locations. This is informational and is not evidence of malware.

Browser protections

Security headers

1 observed
strict-transport-securitypresent max-age=31536000

Response headers

Cookie protections

Passive observation
Cookies observed2
Missing Secure0
Missing HttpOnly1
Missing SameSite0

Only cookie attribute counts are retained. Cookie names and values are never stored. These observations are not proof of compromise and do not independently change the Safety Score.

Detected stack

Technologies

Bootstrap 80% Cloudflare 98% Google Tag Manager 96% Tailwind CSS 72%

Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.

JavaScript library advisories

3 sampled JavaScript files checked locally with Retire.js. Database snapshot: 2026-10-01T02:40:06.962Z.

alpinejs 3.15.11 No known advisories matched this version in the database snapshot.

A version match is not proof that the website is infected or that an issue is exploitable here. Owners should review the advisory, check whether their code is affected and test an update. Up to four external script files are sampled, not every dependency, inline script or dynamically loaded resource.

About this website

What the site says about itself

Welcome.to is a modern link-in-bio platform for creators and businesses. Share all your links, social media, and content in one stunning profile page.

View the site's About page ↗

This is publisher supplied information. The independent safety findings are shown separately.

Structured facts

Website identity & response

Public page metadata
Page titleWelcome.to - One Link for Everything You Share
First headingOne Link for Everything You Share
DescriptionGather all your important links, social media, and content into one beautiful and professional profile page.
Canonical URLhttps://welcome.to/
Final URLhttps://welcome.to/
HTTP response200 · text/html; charset=utf-8 · 1000 ms
Languageen
Structured typesNone observed
Faq page detectedhttps://welcome.to/faq/Page page detectedhttps://welcome.to/blog/About page detectedhttps://welcome.to/about-us/Contact page detectedhttps://welcome.to/contact/
missing100% evidence confidence
1100% evidence confidence
en100% evidence confidence
1100% evidence confidence
1100% evidence confidence
1100% evidence confidence
1100% evidence confidence
8100% evidence confidence
2100% evidence confidence
1100% evidence confidence
unavailable100% evidence confidence
Dns consistency.cname present100% evidence confidence
1100% evidence confidence
Local headers.permissions policy present100% evidence confidence
4100% evidence confidence
Local headers.hsts preload100% evidence confidence
31536000100% evidence confidence
Local headers.hsts include subdomains100% evidence confidence
Local headers.csp present100% evidence confidence
Local headers.cors wildcard origin100% evidence confidence
Local headers.cors present100% evidence confidence
Local headers.cors credentials with wildcard100% evidence confidence
2100% evidence confidence
Local cookies.cookies missing secure100% evidence confidence
Local cookies.cookies missing samesite100% evidence confidence

Connection path

Redirect chain

1 recorded hops
Hop 1https://welcome.to/

The chain is shown exactly as observed by the scanner. A redirect is not itself a malware finding, but unexpected domains or an HTTP downgrade deserve review.

Premium monitoring

Catch downtime and security changes automatically

Regular checks, availability history, and alert emails are reserved for Premium websites. Free reports remain point-in-time scans and do not create recurring server work.

Enable monitoring for this website

Compared with the previous scan

What changed

A comparison will appear after the next completed scan.

Explainable matching

Digital fingerprint

fingerprint-v1
quiet-anchor-wave-851

Comparable components help find technically related websites. A match does not prove common ownership.

DnsHashed private comparison value
TechnologiesHashed private comparison value

Material changes only

Change history

No meaningful changes recorded yet.

Website icon for come.to

Visual evidence

Website screenshot

Screenshot of come.to
Captured once in an isolated browser during this scan. Visual tint is an interface overlay. The original evidence is not duplicated.

For site owners

Show your verified trust report

Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.

Choose a badge style
Preview on your site
WebsiteVirusScanner trust badge preview

Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.

Questions about come.to

FAQ

Still have questions? Contact us →
Is come.to safe to visit?

The latest Safety Score is 63/100 with 75% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.

Did the scan detect malware on come.to?

Local checks reported an indicator that needs investigation. Review the antivirus signature and exact-host phishing results above. These findings are not proof that every page is infected.

When was come.to registered?

The public registry record shows Jul 7, 2024. Registration details may be privacy-protected or updated later.

Did come.to have a valid TLS certificate?

The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.

How does come.to describe itself?

The website's About page describes its purpose in the report above. This is publisher-supplied information and is separate from independent security findings.

Can a paid listing change this website's score?

No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.