megakino.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe1 year old
35
megakino.co was registered on 16 Mar 2025 via Dynadot Inc and the registry expiry is 16 Mar 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/megakino.co.
megakino.co publishes 2 nameservers. DNSSEC is not signed.
megakino.co has 1 IPv4 address (103.224.182.250). The geolocation database places 103.224.182.250 in San Diego, United States.
No safety warning was recorded for megakino.co in the checks that ran.
Domain · RDAP/WHOIS
megakino.co was registered on 16 Mar 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.registry.co/co/domain/megakino.co.
| Registered | since 16 Mar 2025 |
|---|---|
| Created | 16 March 2025 |
| Updated | 21 February 2026 |
| Expires | 16 March 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | 5789.ns1.abovedomains.com, 5789.ns2.abovedomains.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/megakino.co |
megakino.co 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 5789.ns1.abovedomains.com is published for megakino.co in the registration record from https://rdap.registry.co/co/domain/megakino.co.
Nameserver 5789.ns2.abovedomains.com is published for megakino.co in the registration record from https://rdap.registry.co/co/domain/megakino.co.
DNS
megakino.co has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 103.224.182.250 |
|---|---|
| AAAA | — |
| NS | ns1.abovedomains.com, ns2.abovedomains.com |
| MX | park-mx.above.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at megakino.co is "v=spf1 ip6:fdcf:abda:4154::/48 -all".
IPv4 address 103.224.182.250 answers for megakino.co at resolver 1.1.1.1:53.
Mail exchanger park-mx.above.com has preference 10.
A random label under megakino.co also resolved, which means wildcard DNS is on.
Hosting and geo
megakino.co is placed in San Diego, United States by the local geolocation database (db-ip).
| Address | 103.224.182.250 |
|---|---|
| Country | United States |
| City | San Diego |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for megakino.co on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 103.224.182.250:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for megakino.co is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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: rdap created changed from empty to 2025-03-16T17:00:02.0Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from empty to 2027-03-16T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to 5789.ns1.abovedomains.com,5789.ns2.abovedomains.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Dynadot Inc.
- October 2026: rdap statuses changed from empty to client transfer prohibited.
- October 2026: rdap updated changed from empty to 2026-02-21T19:47:02.0Z.
- October 2026: tls issuer changed from YE2 to empty.
- October 2026: tls not_after changed from 2026-12-25T04:10:18Z to empty.
- October 2026: tls protocol changed from TLS 1.3 to empty.
- October 2026: tls valid changed from true to false.
- October 2026: http status_class changed from 2xx to empty.
- October 2026: tech removed Apache HTTP Server.
- October 2026: geo city changed from empty to San Diego.
- October 2026: geo country changed from empty to United States.
Questions
Is megakino.co 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 megakino.co?
megakino.co is placed in San Diego, United States.
When does megakino.co expire?
megakino.co expires on 16 March 2027 according to https://rdap.registry.co/co/domain/megakino.co.
Who owns megakino.co?
The registry did not return a person or a company for megakino.co. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.registry.co/co/domain/megakino.co at 2026-10-30T13:39:19Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:39:19Z
- TLS source tls:443 at 2026-10-30T13:39:19Z
- HTTP source https://megakino.co/ at 2026-10-30T13:39:19Z
- Tech source not available at 2026-10-30T13:39:19Z
- Geo source db-ip at 2026-10-30T13:39:19Z
- Safety source family DNS and local lists at 2026-10-30T13:39:19Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.