eqsl.cc

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 35 days left26 years oldTranco #125282

One re-check per domain each UTC day.

70

eqsl.cc was registered on 12 Apr 2000 via eNom, LLC and the registry expiry is 12 Apr 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc.

eqsl.cc publishes 2 nameservers. DNSSEC is not signed.

eqsl.cc has 1 IPv4 address (46.253.136.27). The geolocation database places 46.253.136.27 in St Louis, United States.

The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 35 days left (TLS 1.2). The homepage answered HTTP 200.

Tech detection named IIS, Microsoft ASP.NET and Windows Server. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for eqsl.cc in the checks that ran.

Domain · RDAP/WHOIS

eqsl.cc was registered on 12 Apr 2000 via eNom, LLC. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc.

Registeredsince 12 Apr 2000
Created12 April 2000
Updated31 March 2026
Expires12 April 2027
RegistrareNom, LLC
Statusclient transfer prohibited
Nameserversns1.hostek.com, ns2.hostek.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc

eqsl.cc carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver ns1.hostek.com is published for eqsl.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc.

Nameserver ns2.hostek.com is published for eqsl.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc.

DNS

eqsl.cc has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A46.253.136.27
AAAA—
NSns1.hostek.com, ns2.hostek.com
MXmail.eqsl.cc (10)
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at eqsl.cc is "v=spf1 ip4:46.253.136.27 include:spf.ezhostingserver.com -all".

IPv4 address 46.253.136.27 answers for eqsl.cc at resolver 1.1.1.1:53.

Mail exchanger mail.eqsl.cc has preference 10.

A random label under eqsl.cc also resolved, which means wildcard DNS is on.

Hosting and geo

eqsl.cc is placed in St Louis, United States by the local geolocation database (db-ip).

Address46.253.136.27
CountryUnited States
CitySt Louis
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for eqsl.cc is valid, with 35 days left and 2 subject alternative names. Source: tls:443.

IssuerGoDaddy TLS Intermediate CA DV - R1v1
Subjecteqsl.cc
Valid from6 September 2026
Valid until5 December 2026
Days left35
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: eqsl.cc, www.eqsl.cc.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • IIS · Web servers
  • Microsoft ASP.NET · Web frameworks
  • Windows Server · Operating systems

IIS is filed under Web servers.

Microsoft ASP.NET is filed under Web frameworks.

Windows Server is filed under Operating systems.

On-page checks

The homepage returned HTTP 200 in 122 ms. The target title is 40 characters and the page has 0 H1 headings.

Status200
TTFB122 ms
Title length40 yes
Quoted title"eQSL.cc - The Electronic QSL Card Centre"
Meta description"The Electronic QSL Card Centre" yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots metaALL
Canonical—
Language—
Links4
Images6
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for eqsl.cc is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to St Louis.
  • October 2026: geo country changed from empty to United States.

Questions

Is eqsl.cc safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts eqsl.cc?

eqsl.cc is placed in St Louis, United States.

When does eqsl.cc expire?

eqsl.cc expires on 12 April 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc.

Who owns eqsl.cc?

The registry did not return a person or a company for eqsl.cc. RDAP often redacts the registrant. The registrar on file is eNom, LLC.

Sources

  • RDAP source https://tld-rdap.verisign.com/cc/v1/domain/eqsl.cc at 2026-10-30T13:33:52Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:33:52Z
  • TLS source tls:443 at 2026-10-30T13:33:52Z
  • HTTP source https://eqsl.cc/ at 2026-10-30T13:33:52Z
  • Tech source wappalyzergo at 2026-10-30T13:33:52Z
  • Geo source db-ip at 2026-10-30T13:33:52Z
  • Safety source family DNS and local lists at 2026-10-30T13:33:52Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.cc eNom, LLC

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.