flasmr.link
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 84 days leftUnder 1 year old
62
flasmr.link was registered on 1 Mar 2026 via Dynadot, LLC and the registry expiry is 1 Mar 2027. WHOIS data came from RDAP at https://rdap.uniregistry.net/rdap/domain/flasmr.link.
flasmr.link publishes 2 nameservers. DNSSEC is not signed.
flasmr.link has 2 IPv4 addresses (104.21.18.122, 172.67.181.209) and 2 IPv6 addresses (2606:4700:3030::6815:127a, 2606:4700:3032::ac43:b5d1). The geolocation database places 104.21.18.122 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 84 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for flasmr.link in the checks that ran.
Domain · RDAP/WHOIS
flasmr.link was registered on 1 Mar 2026 via Dynadot, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.uniregistry.net/rdap/domain/flasmr.link.
| Registered | since 1 Mar 2026 |
|---|---|
| Created | 1 March 2026 |
| Updated | 29 June 2026 |
| Expires | 1 March 2027 |
| Registrar | Dynadot, LLC |
| Status | active |
| Nameservers | fattouche.ns.cloudflare.com, tessa.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.uniregistry.net/rdap/domain/flasmr.link |
Nameserver fattouche.ns.cloudflare.com is published for flasmr.link in the registration record from https://rdap.uniregistry.net/rdap/domain/flasmr.link.
Nameserver tessa.ns.cloudflare.com is published for flasmr.link in the registration record from https://rdap.uniregistry.net/rdap/domain/flasmr.link.
DNS
flasmr.link has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.18.122, 172.67.181.209 |
|---|---|
| AAAA | 2606:4700:3030::6815:127a, 2606:4700:3032::ac43:b5d1 |
| NS | fattouche.ns.cloudflare.com, tessa.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.18.122 answers for flasmr.link at resolver 1.1.1.1:53.
IPv4 address 172.67.181.209 answers for flasmr.link at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:127a answers for flasmr.link at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:b5d1 answers for flasmr.link at resolver 1.1.1.1:53.
A random label under flasmr.link also resolved, which means wildcard DNS is on.
Hosting and geo
flasmr.link is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.18.122 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for flasmr.link is valid, with 84 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | flasmr.link |
| Valid from | 25 October 2026 |
| Valid until | 23 January 2027 |
| Days left | 84 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.flasmr.link, flasmr.link.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 25 ms. The target title is 7 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 25 ms |
| Title length | 7 yes |
| Quoted title | "welcome" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | x-default |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 flasmr.link 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 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 0 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 2 of 5. Five points at one year, two points at 30 days.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is flasmr.link 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 flasmr.link?
flasmr.link is placed in Toronto, Canada.
When does flasmr.link expire?
flasmr.link expires on 1 March 2027 according to https://rdap.uniregistry.net/rdap/domain/flasmr.link.
Who owns flasmr.link?
The registry did not return a person or a company for flasmr.link. RDAP often redacts the registrant. The registrar on file is Dynadot, LLC.
Sources
- RDAP source https://rdap.uniregistry.net/rdap/domain/flasmr.link at 2026-10-30T14:41:47Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:41:47Z
- TLS source tls:443 at 2026-10-30T14:41:47Z
- HTTP source https://flasmr.link/ at 2026-10-30T14:41:47Z
- Tech source wappalyzergo at 2026-10-30T14:41:47Z
- Geo source db-ip at 2026-10-30T14:41:47Z
- Safety source family DNS and local lists at 2026-10-30T14:41:47Z
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.