bulksender.app

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

Online · 200SafeSSL: 53 days left8 years old

One re-check per domain each UTC day.

70

bulksender.app was registered on 25 Oct 2018 via GoDaddy.com, LLC and the registry expiry is 25 Oct 2028. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/bulksender.app.

bulksender.app publishes 2 nameservers. DNSSEC is not signed.

bulksender.app has 3 IPv4 addresses (104.26.12.38, 104.26.13.38, 172.67.70.74) and 3 IPv6 addresses (2606:4700:20::681a:c26, 2606:4700:20::681a:d26, 2606:4700:20::ac43:464a). The geolocation database places 104.26.12.38 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 53 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, Fastly, GitHub Pages, Node.js, Nuxt.js, Varnish and Vue.js. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for bulksender.app in the checks that ran.

Domain · RDAP/WHOIS

bulksender.app was registered on 25 Oct 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://pubapi.registry.google/rdap/domain/bulksender.app.

Registeredsince 25 Oct 2018
Created25 October 2018
Updated10 October 2025
Expires25 October 2028
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserversigor.ns.cloudflare.com, nicole.ns.cloudflare.com
DNSSECno
Sourcehttps://pubapi.registry.google/rdap/domain/bulksender.app

bulksender.app carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.

bulksender.app carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.

bulksender.app 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.

bulksender.app carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.

Nameserver igor.ns.cloudflare.com is published for bulksender.app in the registration record from https://pubapi.registry.google/rdap/domain/bulksender.app.

Nameserver nicole.ns.cloudflare.com is published for bulksender.app in the registration record from https://pubapi.registry.google/rdap/domain/bulksender.app.

DNS

bulksender.app has 6 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.26.12.38, 104.26.13.38, 172.67.70.74
AAAA2606:4700:20::681a:c26, 2606:4700:20::681a:d26, 2606:4700:20::ac43:464a
NSigor.ns.cloudflare.com, nicole.ns.cloudflare.com
MXmxa.mailgun.org (10), mxb.mailgun.org (10)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at bulksender.app is "v=spf1 include:mailgun.org ~all".

IPv4 address 104.26.12.38 answers for bulksender.app at resolver 1.1.1.1:53.

IPv4 address 104.26.13.38 answers for bulksender.app at resolver 1.1.1.1:53.

IPv4 address 172.67.70.74 answers for bulksender.app at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:c26 answers for bulksender.app at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:d26 answers for bulksender.app at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::ac43:464a answers for bulksender.app at resolver 1.1.1.1:53.

Mail exchanger mxa.mailgun.org has preference 10.

Mail exchanger mxb.mailgun.org has preference 10.

Hosting and geo

bulksender.app is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.26.12.38
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for bulksender.app is valid, with 53 days left and 3 subject alternative names. Source: tls:443.

IssuerWE1
Subjectbulksender.app
Valid from25 September 2026
Valid until24 December 2026
Days left53
SAN count3
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.rpc.bulksender.app, bulksender.app, rpc.bulksender.app.

Tech stack

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

  • Cloudflare · CDN
  • Fastly · CDN
  • GitHub Pages · PaaS
  • Node.js · Programming languages
  • Nuxt.js · JavaScript frameworks, Web frameworks, Web servers, Static site generator
  • Varnish · Caching
  • Vue.js · JavaScript frameworks

Cloudflare is filed under CDN.

Fastly is filed under CDN.

GitHub Pages is filed under PaaS.

Node.js is filed under Programming languages.

Nuxt.js is filed under JavaScript frameworks, Web frameworks, Web servers, Static site generator.

Varnish is filed under Caching.

Vue.js is filed under JavaScript frameworks.

On-page checks

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

Status200
TTFB252 ms
Title length16 yes
Quoted title"Token Bulksender"
Meta description"Send ethers,erc20 tokens and NFTs (erc721 and erc1155) in batch. Supported: Ethereum & BSC & MATIC & Almost all EVM-compatible chains. Batch sender. Bulk Sender. Multisender" yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links3
Images17
Faviconyes

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 bulksender.app 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

First checked on 30 October 2026; changes will appear here.

Questions

Is bulksender.app 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 bulksender.app?

bulksender.app is placed in Toronto, Canada.

When does bulksender.app expire?

bulksender.app expires on 25 October 2028 according to https://pubapi.registry.google/rdap/domain/bulksender.app.

Who owns bulksender.app?

The registry did not return a person or a company for bulksender.app. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

  • RDAP source https://pubapi.registry.google/rdap/domain/bulksender.app at 2026-10-30T13:31:23Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:31:23Z
  • TLS source tls:443 at 2026-10-30T13:31:23Z
  • HTTP source https://bulksender.app/ at 2026-10-30T13:31:23Z
  • Tech source wappalyzergo at 2026-10-30T13:31:23Z
  • Geo source db-ip at 2026-10-30T13:31:23Z
  • Safety source family DNS and local lists at 2026-10-30T13:31:23Z

Methodology

Related reports

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

.app GoDaddy.com, 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.