capi.events
Open in
urlscan Pro
2a06:98c1:58::60
Public Scan
Submission: On October 18 via api from IN — Scanned from DE
Summary
TLS certificate: Issued by WE1 on October 9th 2024. Valid for: 3 months.
This is the only time capi.events was scanned on urlscan.io!
urlscan.io Verdict: No classification
Domain & IP information
| IP Address | AS Autonomous System | ||
|---|---|---|---|
| 2 | 2a06:98c1:58::60 2a06:98c1:58::60 | 13335 (CLOUDFLAR...) (CLOUDFLARENET) | |
| 2 | 1 |
| Apex Domain Subdomains |
Transfer | |
|---|---|---|
| 2 |
capi.events
capi.events |
588 B |
| 2 | 1 |
| Domain | Requested by | |
|---|---|---|
| 2 | capi.events | |
| 2 | 1 |
This site contains no links.
| Subject Issuer | Validity | Valid | |
|---|---|---|---|
| capi.events WE1 |
2024-10-09 - 2025-01-07 |
3 months | crt.sh |
This page contains 1 frames:
Primary Page:
https://capi.events/
Frame ID: BEDBA5D1D174D1970CC5864B67CFDD5E
Requests: 2 HTTP requests in this frame
0 Outgoing links
These are links going to different origins than the main page.
Redirected requests
There were HTTP redirect chains for the following requests:
2 HTTP transactions
| Method Protocol |
Resource Path |
Size x-fer |
Type MIME-Type |
||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
GET H2 |
Primary Request
/
capi.events/ |
56 B 476 B |
Document
application/json |
||||||||||||||||||||||||||||||||||||||||||||||
|
General
Request headers
Response headers
|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
GET H2 |
favicon.ico
capi.events/ |
67 B 112 B |
Other
application/json |
||||||||||||||||||||||||||||||||||||||||||||||
|
General
Request headers
Response headers
|
|||||||||||||||||||||||||||||||||||||||||||||||||
Verdicts & Comments Add Verdict or Comment
0 JavaScript Global Variables
These are the non-standard "global" variables defined on the window object. These can be helpful in identifying possible client-side frameworks and code.
1 Cookies
Cookies are little pieces of information stored in the browser of a user. Whenever a user visits the site again, he will also send his cookie values, thus allowing the website to re-identify him even if he changed locations. This is how permanent logins work.
| Domain/Path | Expires | Name / Value |
|---|---|---|
| .capi.events/ | Name: __cf_bm Value: RrlBIL9aRja_CcueuJUd8y2Tgk37ey49a.WrrxNiUBU-1729279245-1.0.1.1-ebyT6Nx4_SoP2m.gXUEpXjYYGomgygzZr7cgvLu5StFhse10f0TRPWsgj2g4lfZbyACk_N5RzeKBqyMqrnwq7Q |
2 Console Messages
A page may trigger messages to the console to be logged. These are often error messages about being unable to load a resource or execute a piece of JavaScript. Sometimes they also provide insight into the technology behind a website.
| Source | Level | URL Text |
|---|
Indicators
This is a term in the security industry to describe indicators such as IPs, Domains, Hashes, etc. This does not imply that any of these indicate malicious activity.
capi.events
2a06:98c1:58::60
17d5328f0d4f4727e8365ee6ea4ef77a88fc515f300058eb06f7a54ecca8b90f
219b6fa838fa483d54ddb8ba42dff0fb89504257fbef94ae5f2ae6e47fa37a39