oto.com — domain analysis
oto.com blocks automated analysis, answering with HTTP 403 to an automated client instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis.
It answered our request with HTTP 403 to an automated client rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.
How does oto.com compare with other domains analysed here?
Measured against the 79 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 28% of them (median 378ms) |
|---|---|
| Domain age | Older than 87% of them |
Related domains in this index
Other analysed domains served from the same country:
When was oto.com registered?
oto.com was registered on 24 May 1995, which makes it about 31 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Marcaria International LLC.
Registration runs until 23 May 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 24 May 1995 |
|---|---|
| Expires | 23 May 2027 |
| Registrar | Marcaria International LLC |
| Registry status | client transfer prohibited |
Where is oto.com hosted?
The first address resolves to infrastructure in Kansas City, United States.
The network is operated by Google Cloud (AS396982 Google LLC).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is oto.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of oto.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 403 over
HTTPS.
At 641ms to first byte this response is slow for a homepage measured from a single European location.
No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.
| Server header | not disclosed |
|---|---|
| Compression | none |
| Page size | 134 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is oto.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-03, which is 59 days from the date of this check. It covers
7 hostnames.
- www.oto.com
- oto.com
- www.zigwheels.ph
- zigwheels.ph
- my.oto.com
- my.zigwheels.ph
- my.zigwheels.my
The certificate has 59 days left to run.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for oto.com?
| IP addresses | 34.107.212.109 |
|---|---|
| Reverse DNS | 109.212.107.34.bc.googleusercontent.com |
| Name servers | ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com |
| Mail (MX) | alt1.aspmx.l.google.com (pri 5), inbound-smtp.us-east-1.amazonaws.com (pri 10), aspmx3.googlemail.com (pri 50), aspmx.l.google.com (pri 1), alt2.aspmx.l.google.com (pri 30), aspmx2.googlemail.com (pri 40), aspmx.l.google.com (pri 10), alt2.aspmx.l.google.com (pri 5), alt4.aspmx.l.google.com (pri 10), alt3.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 20) |
| SPF | v=spf1 include:_spf.google.com include:spf.falconide.com include:ncfp.asia ~all |
| TXT records | 7 |
oto.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 11 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 109.212.107.34.bc.googleusercontent.com, which usually names the hosting provider.
Can oto.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does oto.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own oto.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →
⚠ নিরাপদ থাকুন
জানি একটি স্বাধীন গাইড, কোনো সরকারি ওয়েবসাইট নয়। প্রকৃত কাজটি শুধু অফিসিয়াল পোর্টালেই করুন। যিনি ফোন, মেসেজ বা "সহায়তা"র নামে আপনার NID নম্বর, OTP, পাসওয়ার্ড বা কার্ডের তথ্য চান — কাউকে তা দেবেন না; কোনো প্রকৃত সংস্থা এসব চায় না।
জানি একটি স্বাধীন গাইড এবং কোনো সরকারি সংস্থার সাথে সম্পৃক্ত নয়। ফি, লিংক ও ধাপ পরিবর্তন হতে পারে — কাজ করার আগে সবসময় অফিসিয়াল পোর্টালে নিশ্চিত করে নিন। এটি সাধারণ তথ্য, আইনি বা আর্থিক পরামর্শ নয়।