Website profiles · Technology insights · Alternatives

formcrab.com

Stop putting your personal email on websites. Get a private link to receive messages safely without spam.

Paid content Multilingual
Visit website
Profile views 7 Outbound visits 1 Normal
FormCrab.com Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
Paid contentObserved
Registered
2026
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is FormCrab.com?

FormCrab.com is a contact-form service built around one idea: you share a link instead of your email address. Visitors who want to reach you fill in a form at your private FormCrab link, and the message is forwarded to your real inbox — which stays hidden from the page, from scrapers, and from anyone who copies your contact details.

What it actually does

  • Gives you a private form URL (the page shows an example like formcrab.com/f/user_link) that you can post anywhere you'd normally write "email me at…".
  • Keeps your address in the backend, so it never appears in your page source or bio.
  • Runs bot filtering so automated spam submissions are rejected before they reach you.
  • Stores messages in a panel for 30 days, then deletes them — the site frames this as a privacy feature rather than a permanent archive.

Who it's for

The listed use cases are places where a public email address is normal but risky: GitHub READMEs, social bios, Linktree-style link pages, Notion public pages, static blogs and personal sites. If you're a developer, freelancer, student or hobbyist who wants inbound messages without publishing your address, that's the intended fit. It's less useful if you need a shared team inbox, ticketing, or CRM-style workflows — nothing in the page evidence suggests those.

The trade-off to weigh

A form link adds one step for the sender compared with a plain mailto: address, and some people simply won't bother. In exchange you get a cleaner inbox and no exposed address. The 30-day retention is also a real consideration: if you treat your mail client as the record, that's fine; if you rely on the FormCrab panel as an archive, it isn't.

Next step

Open FormCrab.com and check the pricing page before committing, since cost and any limits on the number of links or submissions are the deciding factors once you know the spam blocking works for your traffic. If you'd rather compare, a general-purpose form backend such as Formspree solves a similar problem with a different feature set.

How does FormCrab hide my email address from website visitors?

FormCrab replaces your real email address with a private link that you share instead. Visitors see and use the link — something like formcrab.com/f/user_link — and never see the email address behind it. When someone submits the form on that link page, the message is forwarded to your real inbox by FormCrab's backend, so your address stays hidden from anyone browsing your site.

The hiding works on two levels:

  • From human visitors: Your address is never displayed on the page, so a person reading your site or social bio has nothing to copy.
  • From automated scrapers: Spam bots that crawl pages looking for written email patterns find only the link, not an address. FormCrab also describes a bot-blocking step that screens automated submissions before they reach you.

This is different from simply obfuscating an address in HTML, where the address is still present in the page source and can be harvested. With FormCrab, the address lives in the service's backend rather than on your page at all.

A practical scenario: You maintain a small personal site and want a contact option without publishing your address. You place your FormCrab link on the contact page and in your social bio. A recruiter or reader fills in the form; the message arrives in your inbox. A scraping bot that hits the same page gets a link it cannot turn into an email address.

Next step: Before committing, test the flow yourself — create a link, submit a message through it, and confirm it lands in your inbox and that replying works the way you expect. Also check the retention detail FormCrab states: messages stay in your panel for 30 days before deletion, so if you need a long-term archive, save copies elsewhere.

Is FormCrab free to use, or does it require a paid subscription?

FormCrab is not positioned as a fully free, unlimited service. Its own site has a dedicated Pricing page, which means there is a paid tier or subscription option. The page itself does not state what the free allowance is, so treat “free to try” and “free forever” as different claims.

What the page does confirm

  • You can get a private link without writing code, and the signup flow is described as taking about 30 seconds.
  • Messages are delivered to your inbox and kept in a panel for 30 days before deletion.
  • The core value is hiding your real address and filtering bot submissions, not unlimited message volume.

How to decide

If you only need a contact link for a GitHub README, a social bio or a small personal site, a free or entry-level plan is usually enough, because volume is low. If you run a business site, a newsletter or a public project where many people may write to you, check the paid tier for message limits, retention and custom domain support before committing.

The practical next step is to open the pricing page, compare the free limits against your expected monthly message count, and only upgrade if you would lose messages or need longer storage than the free tier allows.

How does FormCrab block spam bots from submitting messages?

FormCrab's page describes bot blocking in general terms: automated spam bots are "instantly tested and turned away at our door," and bad email collectors are "turned away." It presents this as an automatic part of using a private form link rather than something you configure, and it does not name the specific technique (for example, a CAPTCHA, a honeypot field, or a JavaScript challenge).

What is concrete on the page:

  • Your address is never rendered in the page. Visitors see a link such as formcrab.com/f/user_link; your real email stays in FormCrab's backend. Scrapers that harvest plain-text addresses have nothing to grab.
  • Messages pass through a filter before reaching you. The page claims only "real entries written by real visitors" get through, with spam blocked at submission time.
  • Retention is limited. Messages land in your mailbox and stay in the panel for 30 days before deletion.

The practical takeaway: FormCrab's main defense is obscuring the address, not sophisticated bot detection. That defeats the most common spam source — address harvesting — but a determined human or a bot that simply fills in any public form can still submit. If you need stronger guarantees, look for a service that documents its method.

For comparison, established form backends publish exactly how they filter:

Service Documented anti-spam approach
Formspree reCAPTCHA plus server-side filtering
Getform reCAPTCHA, honeypot and keyword filters
Web3Forms Honeypot field and spam-domain blocking

Next step: put the link on one low-traffic page first (a GitHub README or social bio) and watch your inbox for a week. If junk still arrives, you need a form service with a visible challenge, since a hidden-address link alone will not stop a bot that submits every form it finds.

How long does FormCrab store my messages before deleting them?

FormCrab says messages are kept inside your panel for 30 days and then deleted. That is the retention window stated on its own page, and it applies to the copy stored in your FormCrab panel rather than to the copy delivered to your real inbox.

The distinction matters in practice. FormCrab's model is that a message is forwarded to the email address you nominate, so a delivered message lives in your mailbox under whatever retention rules you or your email provider apply. The 30-day clock governs the panel-side record. In other words, deleting from the panel is not the same as deleting from your inbox, and vice versa.

A useful way to think about the trade-off:

  • Short panel retention (30 days) limits how long a hosted copy of your messages exists, which reduces exposure if the service is ever breached.
  • Forwarded copies persist wherever your mailbox keeps them, so your email provider's retention and your own archiving habits still determine the long-term footprint.
  • Anything you need later should be saved deliberately — export or file the message before the panel copy ages out.

If you are evaluating this for a public contact link on a GitHub README, social bio or personal site, the practical test is simple: send yourself a test message, confirm it arrives at your real address, then check the panel to see the stored copy and how it is presented. That tells you whether the panel is a convenience inbox or something you would rely on as a record.

For comparison, services built around the same idea include SimpleLogin and addy.io, which approach email concealment through aliases rather than a hosted message panel — a different retention model worth understanding before you commit.

Can I use FormCrab on GitHub, social media bios, or personal websites?

Yes. FormCrab is designed for exactly those placements: its page lists GitHub readmes, social bios, Linktree-style link pages, Notion public pages, static blogs and personal sites as places to share your private form link. The idea is that instead of writing your real address where scrapers can harvest it, you publish a link such as formcrab.com/f/user_link; visitors write through that page, and the message is forwarded to your real inbox.

H3 What each placement looks like in practice

  • GitHub: Put the link in your profile README or a repo's contact section. This is useful for open-source maintainers who want bug reports or collaboration requests without publishing an address that ends up on spam lists.
  • Social bios: Instagram, X, TikTok and similar profiles usually allow only one link, so a form link can double as your contact method. Suits creators, freelancers and anyone who gets DMs but wants a record in email.
  • Personal sites and blogs: Add it to a contact page or footer. Better than a mailto: link, which is trivial for bots to scrape.
  • Link-in-bio pages and Notion: Works anywhere a URL can be pasted, since there is no embed code or widget required.

H3 Trade-offs to weigh

A form link adds one step: visitors land on a separate page rather than opening their mail client directly, which can reduce the number of people who actually write. It also means your contact flow depends on a third-party service staying online. On the other side, the page states that messages are stored in your panel for 30 days and then deleted, and that automated bot submissions are filtered — so you trade a little friction for a cleaner, more private inbox.

H3 A quick decision rule

If your address is already public and you are comfortable with spam filtering at your mail provider, a plain contact form on your own site may be enough. If you want to keep your address entirely off the web while still accepting messages from strangers, a link-based service like this fits GitHub, bios and personal sites well.

Next step: create one link and test it from a logged-out browser, then check that the message arrives in the inbox you chose before you paste it into your README or bio. For alternatives with the same link-based approach, compare Formspree and Contact Form 7 if you would rather host the form yourself.

Related questions

More questions →
How FormCrab Blocks Spam Bots From Contacting You

FormCrab blocks spam bots by never exposing your real email address in the first place. Instead of publishing your address, you share a private form link (formcrab.com/f/your_link). Messages submitted through that link are screened before they reach your inbox: automated bots are "instantly tested and turned away at our door," while only real entries written by real visitors pass through. You don't configure filters or blocklists yourself — the screening happens on FormCrab's side.

The two layers of protection

FormCrab's anti-spam approach works in sequence, and each layer addresses a different failure mode.

Layer 1: Your address is never published

The most common way spam finds you is scraping. Bots crawl websites, social bios, and code pages looking for anything that looks like an email address, then sell or reuse those addresses for spam lists. FormCrab's site describes this directly: "Bad computer programs quickly scan websites to steal written email addresses."

Because your real address stays "private in our backend system," there is nothing on your page for a scraper to collect. This layer doesn't filter spam — it removes the input spam depends on.

Layer 2: Submissions are screened before delivery

Hiding your address stops scrapers, but it doesn't stop someone (or something) from filling out the form itself. That's what the second layer handles. According to FormCrab, "Automated spam bots are instantly tested and turned away at our door," and "Only real entries written by real visitors pass through safely to your clean inbox."

The site frames this as a "Smart Bot Blocker" that runs automatically. There is no mention of a user-facing rule builder, keyword blocklist, or CAPTCHA configuration — the screening is presented as built in.

What this actually protects you from

Threat How FormCrab addresses it
Address scraping by bots Your real email is never shown; only the form link is public
Automated marketing/spam submissions Bot submissions are tested and rejected before delivery
Phishing and scam messages Scammers can't find your real address to target directly
Long-term data exposure Messages are kept in the panel for 30 days, then deleted

The phishing and scam row is worth noting: FormCrab's argument is that "Hackers find your real address easily" when it's public, so hiding it removes you as an easy target. That's a reduction in exposure, not a guarantee that no malicious message ever reaches you.

What you don't have to do

FormCrab's pitch is explicitly low-effort. The site says the setup is "Ready in 30 seconds" and that the links are "Ready-To-Use" with "No code or setup needed." In practice that means:

  • No filter rules to write or maintain
  • No allowlists or blocklists to curate
  • No spam-folder triage as a routine habit

If you've used a form plugin or a self-hosted contact form before, the difference is that spam handling isn't a task you own — it's part of the product.

Where the link can go

The same link works anywhere you'd otherwise paste an email address. FormCrab lists GitHub Readmes, social bios, Linktree links, Notion public pages, static blogs, and personal sites. In each case the trade is the same: visitors get a working way to reach you, and you avoid publishing the address itself.

A realistic example

Say you maintain a small open-source project and want a contact method in your README. The usual move is to write [email protected] in the file. Within days, scrapers can pick that up and your inbox starts collecting marketing mail and fake "your account has been suspended" phishing attempts.

With FormCrab, the README instead contains formcrab.com/f/your_link. A real user with a genuine question fills out the form and the message reaches you. A bot that crawls the README finds a form URL, not an address — and if it tries to submit through the form, the bot screening rejects it.

What to verify before relying on it

The mechanism described is credible for the two problems it targets (scraping and automated form submissions), but a few things are worth checking yourself rather than assuming:

  • Delivery reliability. The site promises "Safe Mail Delivery Protection," but the only way to know messages actually arrive is to send a test submission and confirm it lands.
  • What "tested" means. FormCrab doesn't publish the specifics of how bots are detected. If your use case attracts targeted (human) spam rather than automated spam, screening designed for bots may not catch it.
  • Retention. Messages live in the panel for 30 days before deletion. If you need a longer archive, forward or export them yourself.
  • Pricing and account requirements. The site links to a pricing page, so check current terms before assuming any tier is free.
How to Set Up a FormCrab Private Link

You can set up a FormCrab private link in about 30 seconds, with no code and no extra configuration. You tell FormCrab which inbox should receive your messages, it generates a clean form page link, and you share that link anywhere you would otherwise post your email address. The result: visitors can write to you, but your real email stays hidden behind the link.

What You Need Before Starting

FormCrab is built for people who want to receive messages without exposing a personal email address on public pages. Before you begin, have the following ready:

  • A working email address you can access — this is where your new messages will be delivered.
  • A place to share the link — for example a GitHub README, a social media bio, a Linktree, a Notion public page, a static blog, or a personal site.
  • No coding tools or hosting setup — the site states that ready-to-use links require no code or setup.

Step-by-Step Setup

Step 1: Tell FormCrab where to send your messages

Enter the email address where you want to receive new messages safely. This address stays private in FormCrab's backend system — it is never shown to the people who contact you.

Expected result: FormCrab knows which inbox to deliver real messages to, while keeping that address invisible to visitors and bots.

Step 2: Get your private link

FormCrab generates a simple, clean form page for you, ready to use instantly. The link follows this pattern:

formcrab.com/f/user_link

Your real email sits hidden behind that link. Anyone who opens it sees a contact form, not your address.

Expected result: You have a shareable URL that collects messages on your behalf.

Step 3: Share the link and let it work

Post the link wherever people might want to reach you:

  • GitHub READMEs
  • Social bios
  • Linktree links
  • Notion public pages
  • Static blogs
  • Personal sites

Expected result: Real visitors submit real messages that arrive in your inbox. Automated spam bots are tested and turned away at the door, so they never reach you.

What Happens to Your Messages and Data

Understanding the flow helps you decide whether this fits your needs:

Stage What happens
Visitor opens your link Sees a clean form page, not your email address
Visitor submits a message The message passes through FormCrab's bot check
Bot traffic Blocked automatically before delivery
Real messages Delivered to your chosen mailbox
Stored messages Kept inside your panel for 30 days, then deleted

The 30-day auto-delete is a deliberate privacy choice: FormCrab states it does not keep your logs forever.

Why This Setup Blocks Spam

The mechanism is straightforward. Spam bots crawl the web looking for written email addresses — the kind you would normally paste into a website page or a Twitter bio. Because FormCrab never displays your address, there is nothing for those bots to scrape. Meanwhile, the form itself screens incoming submissions, so automated entries get rejected while genuine ones go through.

This is why the setup works without any spam-filter configuration on your side: the protection is built into the link rather than added afterward.

Common Questions During Setup

Do I need to write any code? No. The site states that ready-to-use links need no code or setup.

How long does it take? The site describes the process as "ready in 30 seconds" across the three steps above.

Can I use it on more than one page? Yes — the same link can be placed on any page or profile where you want to be reachable.

What if I want to stop receiving messages? Since your email is never exposed, removing the link removes the contact channel. The site does not describe a separate deactivation step in the available material.

When This Setup Makes Sense

Choose FormCrab's private link approach if you want to be contactable on public pages but do not want your personal address scraped, spammed, or targeted by phishing. It fits developers, creators, and anyone maintaining a public profile or personal site.

If you need a full contact-management system with CRM features or team routing, this is a simpler tool focused on one job: hiding your email while still receiving real messages.

What is FormCrab.com and what does it do?

FormCrab.com is a contact-form service that lets you receive messages through a private link instead of publishing your real email address. You share a URL in the form formcrab.com/f/your_link, and messages submitted through it are forwarded to your inbox while your actual address stays hidden in FormCrab's backend. It suits anyone who needs a public contact point — a GitHub README, social bio, Linktree, Notion page, static blog, or personal site — but doesn't want that address scraped, spammed, or phished.

How it works

The mechanism is a relay, not a new mailbox:

  1. You register a destination address. You tell FormCrab where you want new messages delivered.
  2. FormCrab issues a private link. You get a clean form page at a formcrab.com/f/... URL, ready to use immediately.
  3. Visitors submit through the form. They never see your email — it stays in FormCrab's system.
  4. Messages reach your inbox. Entries that pass the bot check are delivered to you; the site says messages are also kept in your panel for 30 days and then deleted.

The site describes the flow as taking about 30 seconds and requiring no code or setup.

What problem it solves

Publishing a raw email address on a public page exposes you to three distinct risks that FormCrab separates out:

Risk What happens with a public email What FormCrab changes
Scraping Bots crawl pages and harvest written addresses for spam lists Your address is never written on the page, so there is nothing to scrape
Junk mail Automated marketing and sales spam floods the inbox Only submissions that pass the bot check are forwarded
Phishing and scams Attackers find the real address and send fake links The real address is not discoverable from the link you share

The trade-off is structural: you gain privacy and spam filtering, but you add a third party between you and your correspondents, and your contact flow depends on that service staying up.

Where it fits

FormCrab lists these placements as intended uses:

  • GitHub READMEs
  • Social media bios
  • Linktree links
  • Notion public pages
  • Static blogs
  • Personal sites

The common thread is a public page where you want a contact option but not a permanent, harvestable address. If you already use a dedicated throwaway address for public contact, FormCrab's main advantage — hiding the address entirely — matters less.

What to check before committing

  • Pricing. The site has a pricing page at formcrab.com/pricing, but the available material doesn't state the cost or whether a free tier exists. Check that page directly before relying on it.
  • Data retention. The stated policy is 30 days in the panel, then deletion. If you need a permanent archive of contact messages, save them from your inbox.
  • Deliverability. Since messages are relayed, confirm that FormCrab's sending domain isn't filtered by your mail provider — send yourself a test submission first.
  • Account requirements. The material doesn't specify what sign-up involves, so treat the "30 seconds" claim as a setup estimate rather than a guarantee.

If your goal is simply to stop spam without changing how people reach you, a masked address or a contact form on your own domain may be sufficient. FormCrab is the better fit when you want the address itself to be invisible and are comfortable routing contact through a third-party link.

How FormCrab Hides Your Email Address While Still Letting People Message You

FormCrab replaces your real email address with a private form link. You give FormCrab the inbox where you want to receive messages, and it gives you back a link like formcrab.com/f/user_link that you can post publicly. Visitors type into that form instead of seeing your address, so scrapers and spam bots have nothing to harvest. Your real email stays in FormCrab's backend, and messages that pass its bot checks get forwarded to you.

The core mechanism

The whole trick is a substitution: a public link in place of a private address.

  1. You provide a destination inbox. FormCrab needs to know where to send the messages people write to you.
  2. FormCrab generates a private link. That link points to a hosted form page, not to your address.
  3. Visitors submit through the form. They see a contact page, never your email.
  4. Your address stays hidden. According to FormCrab, the address "stays private in our backend system," so it is never rendered on the page for bots to scrape.
  5. Messages are forwarded to your inbox. Real submissions reach you; automated ones are filtered out.

Because the address never appears in the page source, the usual scraping approach — crawling sites for anything that looks like [email protected] — has nothing to find.

What happens to a message after it is sent

FormCrab describes a two-stage lifecycle for messages:

Stage What happens
Delivery The message is sent to your mailbox
Retention It is kept inside your panel for 30 days
Deletion After 30 days it is deleted automatically

So the panel is a short-term holding area rather than a permanent archive. If you need a message long-term, keep it in your own mailbox.

Why the link approach blocks spam

FormCrab's comparison of "before" and "after" comes down to three differences:

  • Scraping fails. With a raw address on a page, bots scan and steal it. With a link, there is no address on the page to steal.
  • Bots are tested at the door. FormCrab says automated spam bots are "instantly tested and turned away," so only entries it judges to be from real visitors pass through.
  • Your inbox stays clean. Marketing and sales spam that would normally flood a public address does not arrive, because the address was never exposed.

This is a filter-plus-concealment model, not just an alias. An alias hides the address but still accepts everything sent to it; FormCrab adds a bot check before forwarding.

Where the link works well

FormCrab lists these as intended placements, and they share one trait — a public page where you want contact without publishing an address:

  • GitHub READMEs
  • Social media bios
  • Linktree-style link lists
  • Notion public pages
  • Static blogs
  • Personal sites

If your situation is "strangers should be able to reach me, but I don't want my address in public," this fits. If you need to reply from your real address and want the recipient to see it, that is a different workflow — the form is for inbound contact.

Setup in three steps

FormCrab describes onboarding as taking about 30 seconds:

  1. Hide your real email — tell FormCrab where you want new messages delivered.
  2. Get your private link — FormCrab returns a ready-to-use form page.
  3. Share and relax — post the link; real entries reach you and bots are blocked.

No code or setup is required, which is why it suits static pages and profiles where you cannot run a backend.

Limits worth knowing before you commit

  • Retention is 30 days. Anything you want to keep should be moved out of the panel.
  • You are trusting a third party with your address. The address is hidden from the public, but FormCrab itself holds it.
  • Pricing is not stated in the material reviewed here. FormCrab has a pricing page, but no figures or plan details are given, so check that page directly if cost matters to you.
  • Bot filtering is a judgment call. Any automated filter can occasionally misclassify; treat "only real messages get through" as the design goal rather than a guarantee.

If your goal is simply to stop your address from being scraped off public pages while still receiving genuine messages, the link-plus-filter model addresses exactly that problem.

How Long Does FormCrab Keep My Messages and Data?

FormCrab keeps messages in your panel for 30 days, then deletes them automatically. According to the site, messages are first sent to your mailbox, stored inside your panel for 30 days, and then removed "for your safety." FormCrab also states it does not keep your logs forever. Your real email address stays hidden in the backend system rather than being exposed on the page.

What happens to a message after someone submits it

The flow described on FormCrab is:

  1. A visitor writes to you through your private link (for example, formcrab.com/f/user_link).
  2. The message is delivered to the email address you chose when setting up the link.
  3. A copy is kept inside your FormCrab panel for 30 days.
  4. After 30 days, that copy is deleted automatically.

So the 30-day window applies to the copy held in your panel — not to the message sitting in your own email inbox, which you control.

What FormCrab says about data retention

Data Retention stated on the site
Messages in your panel 30 days, then deleted
Logs Not kept forever
Your real email address Stays private in the backend system

The stated design goal is privacy: keep your address out of public view and avoid holding onto message data longer than needed.

Why this matters for privacy

Showing your real email on a website or social bio makes it easy for scrapers and bots to collect. FormCrab's approach is to give out a link instead, so your address is never written on the page. Combined with the 30-day auto-delete, the idea is to limit both exposure and how long your message data lingers.

Practical implications

  • If you need a long-term archive, save or export messages from your own mailbox — the panel copy disappears after 30 days.
  • If you want minimal data stored, the automatic deletion means you don't have to clean up manually.
  • If you rely on the panel as your only record, set a reminder to check it before the 30-day window closes.

For exact terms, see FormCrab's Terms and Privacy Policy, linked from the site.

Website Overview

Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

The domain was registered less than a year ago and has limited historical evidence to assess. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the NetEase Mail email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Bootstrap, Google Analytics, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Twitter Card metadata is configured. The page declares 10 language or regional alternatives using hreflang. The title has 57 characters, within a common display range. A meta description is present, with 105 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailNetEase Mail
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.23.125

Registration details

RDAP / WHOIS

RegistrarRealtime Register B.V.
Registered2026-05-21
Expires2027-05-21
Domain statusclient transfer prohibited
Nameserversbrad.ns.cloudflare.com、jean.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aformcrab.com104.21.23.125300—
Aformcrab.com172.67.211.22300—
AAAAformcrab.com2606:4700:3036::6815:177d300—
AAAAformcrab.com2606:4700:3037::ac43:d316300—
MXformcrab.comhzmx01.mxmail.netease.com3005
MXformcrab.comhzmx02.mxmail.netease.com30010
NSformcrab.combrad.ns.cloudflare.com86400—
NSformcrab.comjean.ns.cloudflare.com86400—
TXTformcrab.comgoogle-site-verification=W1XcUX9ZzN0P2H6hDhL5nwJOrJDysPI3tP17ubOj8lo300—
TXTformcrab.comv=spf1 include:amazonses.com include:spf.163.com ~all300—
DMARC_dmarc.formcrab.comv=DMARC1; p=none;300—
DMARC_dmarc.formcrab.comv=DMARC1; p=quarantine; fo=1; ruf=mailto:[email protected]; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2
Negotiated protocolTLSv1.2
Certificate subjectformcrab.com
IssuerLet's Encrypt
Valid until2026-12-15T04:38 · Remaining when checked: 72 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html;charset=UTF-8
content-languageen
cache-controlno-cache, no-store, max-age=0, must-revalidate
servercloudflare
x-frame-optionsDENY
x-content-type-optionsnosniff

Identified technologies

BootstrapGoogle AnalyticsCloudflare

Pages, Search and Sharing

Meta descriptionStop putting your personal email on websites. Get a private link to receive messages safely without spam.
Canonical URLhttps://formcrab.com/
LanguageEnglish (default) · Multilingual
Twitter Cardsummary_large_image

Unknown

No sitemaps found

User reviews (0)

  • No reviews yet.