alabidan.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 71 days left14 years old
65
alabidan.me was registered on 18 Jun 2012 via GoDaddy.com, LLC and the registry expiry is 18 Jun 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/alabidan.me.
alabidan.me publishes 2 nameservers. DNSSEC is not signed.
alabidan.me has 4 IPv4 addresses (185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153) and 4 IPv6 addresses (2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153). The geolocation database places 185.199.108.153 in San Francisco (South Beach), United States.
The TLS certificate from YR2 is valid and has 71 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Fastly, GitHub Pages, Google Analytics and Varnish. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for alabidan.me in the checks that ran.
Domain · RDAP/WHOIS
alabidan.me was registered on 18 Jun 2012 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/alabidan.me.
| Registered | since 18 Jun 2012 |
|---|---|
| Created | 18 June 2012 |
| Updated | 11 August 2026 |
| Expires | 18 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns15.domaincontrol.com, ns16.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/alabidan.me |
alabidan.me 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.
alabidan.me 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.
alabidan.me 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.
alabidan.me 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 ns15.domaincontrol.com is published for alabidan.me in the registration record from https://rdap.identitydigital.services/rdap/domain/alabidan.me.
Nameserver ns16.domaincontrol.com is published for alabidan.me in the registration record from https://rdap.identitydigital.services/rdap/domain/alabidan.me.
DNS
alabidan.me has 8 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153 |
|---|---|
| AAAA | 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153 |
| NS | ns15.domaincontrol.com, ns16.domaincontrol.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.199.108.153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv4 address 185.199.109.153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv4 address 185.199.110.153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv4 address 185.199.111.153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv6 address 2606:50c0:8000::153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv6 address 2606:50c0:8001::153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv6 address 2606:50c0:8002::153 answers for alabidan.me at resolver 1.1.1.1:53.
IPv6 address 2606:50c0:8003::153 answers for alabidan.me at resolver 1.1.1.1:53.
Hosting and geo
alabidan.me is placed in San Francisco (South Beach), United States by the local geolocation database (db-ip).
| Address | 185.199.108.153 |
|---|---|
| Country | United States |
| City | San Francisco (South Beach) |
| Source | db-ip |
SSL/TLS
The certificate for alabidan.me is valid, with 71 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | alabidan.me |
| Valid from | 13 October 2026 |
| Valid until | 11 January 2027 |
| Days left | 71 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: alabidan.me, www.alabidan.me.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Fastly · CDN
- GitHub Pages · PaaS
- Google Analytics · Analytics
- Varnish · Caching
Bootstrap is filed under UI frameworks.
Fastly is filed under CDN.
GitHub Pages is filed under PaaS.
Google Analytics is filed under Analytics.
Varnish is filed under Caching.
On-page checks
The homepage returned HTTP 200 in 229 ms. The target title is 15 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 229 ms |
| Title length | 15 yes |
| Quoted title | "Daniel G. Alabi" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 14 |
| Images | 1 |
| 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 alabidan.me 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
- October 2026: rdap created changed from 2012-06-18T02:05:19Z to 2012-06-18T02:05:19.525Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-06-18T02:05:19Z to 2027-06-18T02:05:19.525Z.
- October 2026: rdap statuses changed from clientdeleteprohibited,clientrenewprohibited,clienttransferprohibited,clientupdateprohibited to client delete prohibited,client renew prohibited,client transfer prohibited,client update prohibited.
- October 2026: rdap updated changed from 2026-08-11T20:55:20Z to 2026-08-11T20:55:20.595Z.
- October 2026: geo city changed from empty to San Francisco (South Beach).
- October 2026: geo country changed from empty to United States.
Questions
Is alabidan.me 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 alabidan.me?
alabidan.me is placed in San Francisco (South Beach), United States.
When does alabidan.me expire?
alabidan.me expires on 18 June 2027 according to https://rdap.identitydigital.services/rdap/domain/alabidan.me.
Who owns alabidan.me?
The registry did not return a person or a company for alabidan.me. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/alabidan.me at 2026-10-30T14:43:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:43:36Z
- TLS source tls:443 at 2026-10-30T14:43:36Z
- HTTP source https://alabidan.me/ at 2026-10-30T14:43:36Z
- Tech source wappalyzergo at 2026-10-30T14:43:36Z
- Geo source db-ip at 2026-10-30T14:43:36Z
- Safety source family DNS and local lists at 2026-10-30T14:43:36Z
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.