missionaryboys.com

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

Online · 200Family DNS blockedSSL: 47 days left8 years old

One re-check per domain each UTC day.

50

missionaryboys.com was registered on 19 Sep 2018 via NameCheap, Inc. and the registry expiry is 19 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/missionaryboys.com.

missionaryboys.com publishes 2 nameservers. DNSSEC is not signed.

missionaryboys.com has 3 IPv4 addresses (104.26.4.164, 104.26.5.164, 172.67.72.120) and 3 IPv6 addresses (2606:4700:20::681a:4a4, 2606:4700:20::681a:5a4, 2606:4700:20::ac43:4878). The geolocation database places 104.26.4.164 in Toronto, Canada.

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

Tech detection named Cloudflare, Cloudflare Bot Management, Express, Google Cloud, Google Cloud CDN, Google Tag Manager, HTTP/3, Node.js and React. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

missionaryboys.com was registered on 19 Sep 2018 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/missionaryboys.com.

Registeredsince 19 Sep 2018
Created19 September 2018
Updated20 August 2026
Expires19 September 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversarnold.ns.cloudflare.com, ivy.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/missionaryboys.com

missionaryboys.com 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 arnold.ns.cloudflare.com is published for missionaryboys.com in the registration record from https://rdap.verisign.com/com/v1/domain/missionaryboys.com.

Nameserver ivy.ns.cloudflare.com is published for missionaryboys.com in the registration record from https://rdap.verisign.com/com/v1/domain/missionaryboys.com.

DNS

missionaryboys.com has 6 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.26.4.164, 104.26.5.164, 172.67.72.120
AAAA2606:4700:20::681a:4a4, 2606:4700:20::681a:5a4, 2606:4700:20::ac43:4878
NSarnold.ns.cloudflare.com, ivy.ns.cloudflare.com
MXgmr-smtp-in.l.google.com (5) Google, alt1.gmr-smtp-in.l.google.com (10) Google, alt2.gmr-smtp-in.l.google.com (20) Google, alt3.gmr-smtp-in.l.google.com (30) Google, alt4.gmr-smtp-in.l.google.com (40) Google
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.26.4.164 answers for missionaryboys.com at resolver 1.1.1.1:53.

IPv4 address 104.26.5.164 answers for missionaryboys.com at resolver 1.1.1.1:53.

IPv4 address 172.67.72.120 answers for missionaryboys.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:4a4 answers for missionaryboys.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:5a4 answers for missionaryboys.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::ac43:4878 answers for missionaryboys.com at resolver 1.1.1.1:53.

Mail exchanger gmr-smtp-in.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger alt1.gmr-smtp-in.l.google.com has preference 10. The host is recognised as Google.

Mail exchanger alt2.gmr-smtp-in.l.google.com has preference 20. The host is recognised as Google.

Mail exchanger alt3.gmr-smtp-in.l.google.com has preference 30. The host is recognised as Google.

Mail exchanger alt4.gmr-smtp-in.l.google.com has preference 40. The host is recognised as Google.

Hosting and geo

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

Address104.26.4.164
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for missionaryboys.com is valid, with 47 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectmissionaryboys.com
Valid from19 September 2026
Valid until18 December 2026
Days left47
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.missionaryboys.com, missionaryboys.com.

Tech stack

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

  • Cloudflare · CDN
  • Cloudflare Bot Management · Security
  • Express · Web frameworks, Web servers
  • Google Cloud · IaaS
  • Google Cloud CDN · CDN
  • Google Tag Manager · Tag managers
  • HTTP/3 · Miscellaneous
  • Node.js · Programming languages
  • React · JavaScript frameworks

Cloudflare is filed under CDN.

Cloudflare Bot Management is filed under Security.

Express is filed under Web frameworks, Web servers.

Google Cloud is filed under IaaS.

Google Cloud CDN is filed under CDN.

Google Tag Manager is filed under Tag managers.

HTTP/3 is filed under Miscellaneous.

Node.js is filed under Programming languages.

React is filed under JavaScript frameworks.

On-page checks

The homepage returned HTTP 200 in 32 ms. The target title is 39 characters and the page has 1 H1 heading.

Status200
TTFB32 ms
Title length39 yes
Quoted title"Sayuncle.com: Age Verification Required"
Meta description"Welcome to Sayuncle.com, join now and start the age verification process to gain access to all the premium content." yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots metanoindex
Canonicalhttps://www.sayuncle.com/verify
Languageen
Links54
Images22
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 missionaryboys.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for missionaryboys.com. That resolver covers adult and malware names.

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 0 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 missionaryboys.com safe?

Cloudflare family DNS returned a block for missionaryboys.com. That resolver covers adult and malware names.

Who hosts missionaryboys.com?

missionaryboys.com is placed in Toronto, Canada.

When does missionaryboys.com expire?

missionaryboys.com expires on 19 September 2027 according to https://rdap.verisign.com/com/v1/domain/missionaryboys.com.

Who owns missionaryboys.com?

The registry did not return a person or a company for missionaryboys.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/missionaryboys.com at 2026-10-30T14:04:19Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:04:19Z
  • TLS source tls:443 at 2026-10-30T14:04:19Z
  • HTTP source https://missionaryboys.com/ at 2026-10-30T14:04:19Z
  • Tech source wappalyzergo at 2026-10-30T14:04:19Z
  • Geo source db-ip at 2026-10-30T14:04:19Z
  • Safety source family DNS and local lists at 2026-10-30T14:04:19Z

Methodology

Related reports

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

.com NameCheap, Inc.

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.