boylanfh.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 158 days left9 years old
65
boylanfh.com was registered on 25 Jul 2017 via GoDaddy.com, LLC and the registry expiry is 25 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/boylanfh.com.
boylanfh.com publishes 4 nameservers. DNSSEC is not signed.
boylanfh.com has 4 IPv4 addresses (18.173.205.126, 18.173.205.43, 18.173.205.85, 18.173.205.91). The geolocation database places 18.173.205.126 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 158 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon ALB, Amazon CloudFront, Amazon Web Services, Cloudflare, Google Tag Manager, HTTP/3, IIS, Microsoft ASP.NET, Osano, Vue.js, Windows Server and cdnjs. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for boylanfh.com in the checks that ran.
Domain · RDAP/WHOIS
boylanfh.com was registered on 25 Jul 2017 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/boylanfh.com.
| Registered | since 25 Jul 2017 |
|---|---|
| Created | 25 July 2017 |
| Updated | 3 June 2024 |
| Expires | 25 July 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1192.awsdns-21.org, ns-151.awsdns-18.com, ns-1599.awsdns-07.co.uk, ns-811.awsdns-37.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/boylanfh.com |
boylanfh.com 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.
boylanfh.com 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.
boylanfh.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.
boylanfh.com 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 ns-1192.awsdns-21.org is published for boylanfh.com in the registration record from https://rdap.verisign.com/com/v1/domain/boylanfh.com.
Nameserver ns-151.awsdns-18.com is published for boylanfh.com in the registration record from https://rdap.verisign.com/com/v1/domain/boylanfh.com.
Nameserver ns-1599.awsdns-07.co.uk is published for boylanfh.com in the registration record from https://rdap.verisign.com/com/v1/domain/boylanfh.com.
Nameserver ns-811.awsdns-37.net is published for boylanfh.com in the registration record from https://rdap.verisign.com/com/v1/domain/boylanfh.com.
DNS
boylanfh.com has 4 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.173.205.126, 18.173.205.43, 18.173.205.85, 18.173.205.91 |
|---|---|
| AAAA | — |
| NS | ns-1192.awsdns-21.org, ns-151.awsdns-18.com, ns-1599.awsdns-07.co.uk, ns-811.awsdns-37.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 18.173.205.126 answers for boylanfh.com at resolver 1.1.1.1:53.
IPv4 address 18.173.205.43 answers for boylanfh.com at resolver 1.1.1.1:53.
IPv4 address 18.173.205.85 answers for boylanfh.com at resolver 1.1.1.1:53.
IPv4 address 18.173.205.91 answers for boylanfh.com at resolver 1.1.1.1:53.
A random label under boylanfh.com also resolved, which means wildcard DNS is on.
Hosting and geo
boylanfh.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 18.173.205.126 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for boylanfh.com is valid, with 158 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | boylanfh.com |
| Valid from | 22 September 2026 |
| Valid until | 7 April 2027 |
| Days left | 158 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.boylanfh.com, boylanfh.com.
Tech stack
Tech detection checked the fetched homepage and named 12 products. Source: wappalyzergo.
- Amazon ALB · Load balancers
- Amazon CloudFront · CDN
- Amazon Web Services · PaaS
- Cloudflare · CDN
- Google Tag Manager · Tag managers
- HTTP/3 · Miscellaneous
- IIS · Web servers
- Microsoft ASP.NET · Web frameworks
- Osano · Cookie compliance
- Vue.js · JavaScript frameworks
- Windows Server · Operating systems
- cdnjs · CDN
Amazon ALB is filed under Load balancers.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
Cloudflare is filed under CDN.
Google Tag Manager is filed under Tag managers.
HTTP/3 is filed under Miscellaneous.
IIS is filed under Web servers.
Microsoft ASP.NET is filed under Web frameworks.
Osano is filed under Cookie compliance.
Vue.js is filed under JavaScript frameworks.
Windows Server is filed under Operating systems.
cdnjs is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 393 ms. The target title is 39 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 393 ms |
| Title length | 39 yes |
| Quoted title | "Boylan Funeral Home | New Brunswick, NJ" |
| Meta description | "Boylan Funeral Home in New Brunswick, NJ provides funeral, memorial, aftercare, preplanning, and cremation services to our community and the surrounding ar... Learn More" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | yes |
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 boylanfh.com 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 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 boylanfh.com 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 boylanfh.com?
boylanfh.com is placed in Frankfurt am Main, Germany.
When does boylanfh.com expire?
boylanfh.com expires on 25 July 2027 according to https://rdap.verisign.com/com/v1/domain/boylanfh.com.
Who owns boylanfh.com?
The registry did not return a person or a company for boylanfh.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/boylanfh.com at 2026-10-30T13:47:44Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:44Z
- TLS source tls:443 at 2026-10-30T13:47:44Z
- HTTP source https://boylanfh.com/ at 2026-10-30T13:47:44Z
- Tech source wappalyzergo at 2026-10-30T13:47:44Z
- Geo source db-ip at 2026-10-30T13:47:44Z
- Safety source family DNS and local lists at 2026-10-30T13:47:44Z
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.