Laylax.com LayLax(ライラクス)|エアガン・ガスガン・電動ガン・東京マルイカスタム・サバイバルゲーム装備

LayLax（ライラクス）はエアソフトガン（電動ガン・ガスガン・エアーコッキングガン）のカスタムパーツを企画・設計・開発し、サバイバルゲーム・シューティングマッチをはじめとした全世界のエアソフトガンファンの皆様に喜んでいただくため、この世に生まれたメーカーです。カスタムパーツに限らず、装備品や消耗品...

Laylax.com Overview

Laylax.com ranking shows that the page is at position 1,292,704 over the world.

In terms of rank-to-traffic ratio, laylax.com has 183 unique users per day, viewing 554 pages. The rank based value of laylax.com is 6,314 USD. Every user makes 3.21 pageviews on average.

Laylax.com boasts a link base consisting of 294 referring domains and 335 external backlinks, as revealed by the data obtained from web network scanning.

Laylax.com top-level domain belongs to .COM domain zone. Check other webpages in .COM zone.

According the last verification test in July 04, 2024, laylax.com has an expired SSL certificate issued by Let's Encrypt (expired on August 22, 2024). Click button “Update” SSL Information at the Safety Information section. Check the list of websites using SSL by Let's Encrypt.

Based on data from Google Safe Browsing, Google Safe Search, Symantec and Web of Trust laylax.com is a fairly safe domain.

According the Mobile-Friendly test by Google laylax.com is nice optimized for mobile devices and tablets, however the webpage speed could be improved.

Laylax.com Rank Summary

Global Rank

1,292,704

Average Load Time

0.96sec

Links In Count

Website Value

$5,846

Audience Geography. Where are laylax.com visitors located?

Country	Visitors

Country	Pageviews

Country	Rank

Where do visitors go on laylax.com?

Subdomain	Pageviews

Subdomain	Pageviews per User

Subdomain	Reach

How popular is laylax.com?

Period	Global Rank	Global Rank Delta
past 3 months	1292704	379722

Days	Pageviews Rank	Pageviews Rank Delta	Pageviews per Million	Pageviews per Million Delta	Pageviews per User	Pageviews per User Delta
90	1199731	304091	2	-30.32%	3	8%

Days	Reach Rank	Reach Rank Delta	Reach per Million	Reach per Million Delta
90	1424702	446561	3	-35.54%

Laylax.com Website Safety

Overview

Last Updated: 07/04/2025

Overall result - laylax.com is safe.

We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.

Norton Connect Safe

Last Updated: 03/28/2025

laylax.com is safe.

Norton ConnectSafe evaluates laylax.com for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search

Last Updated: 03/19/2019

laylax.com is safe.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing

Last Updated: 01/09/2019

laylax.com is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.

Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.

Site Advisor

Last Updated: 02/27/2021

laylax.com is safe.

McAfee assesses laylax.com for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze laylax.com for mature or inappropriate content, only security checks are evaluated.

Web of Trust

Last Updated: 01/10/2019

laylax.com child safety is very good.

The WOT calculates reputation of the laylax.com. This reputation system receives ratings from users and information from third-party sources, assesses the laylax.com for safety features and confirms, whether laylax.com is suitable for children.

SSL Information

SSL Checker Tool

Domain	laylax.com
Issuer Organization	Let's Encrypt
Issuer	R3
Algorithm	RSA-SHA256
Valid form	05/24/2024
Expiration	08/22/2024
Signed	Certificate is not self signed
Additional Domains	laylax.com

Laylax.com Rank History

Alexa Rank shows how popular laylax.com is in comparison with other sites. The most popular site has Alexa Rank equals 1. If laylax.com has Alexa Rank equals 100,000, then it is in TOP 100,000 popular sites in the world. The rank is calculated using a combination of average daily visitors to laylax.com and pageviews on laylax.com over the past 3 months.

Laylax.com Hosting Information

Server Location

Geolocation Tool

ASN Information

ASN Lookup Tool

ASN ID: 13335

ASN Title: CLOUDFLARENET - Cloudflare, Inc., US

Last Update: 10/30/2024

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 13335
ASName: CLOUDFLARENET
ASHandle: AS13335
RegDate: 2010-07-14
Updated: 2017-02-17
Comment: All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse
Ref: https://rdap.arin.net/registry/autnum/13335

OrgName: Cloudflare, Inc.
OrgId: CLOUD14
Address: 101 Townsend Street
City: San Francisco
StateProv: CA
PostalCode: 94107
Country: US
RegDate: 2010-07-09
Updated: 2017-02-17
Comment: All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse
Ref: https://rdap.arin.net/registry/entity/CLOUD14

OrgTechHandle: ADMIN2521-ARIN
OrgTechName: Admin
OrgTechPhone: +1-650-319-8930
OrgTechEmail: rir@cloudflare.com
OrgTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN

OrgAbuseHandle: ABUSE2916-ARIN
OrgAbuseName: Abuse
OrgAbusePhone: +1-650-319-8930
OrgAbuseEmail: abuse@cloudflare.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN

OrgNOCHandle: NOC11962-ARIN
OrgNOCName: NOC
OrgNOCPhone: +1-650-319-8930
OrgNOCEmail: noc@cloudflare.com
OrgNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN

RNOCHandle: NOC11962-ARIN
RNOCName: NOC
RNOCPhone: +1-650-319-8930
RNOCEmail: noc@cloudflare.com
RNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN

RTechHandle: ADMIN2521-ARIN
RTechName: Admin
RTechPhone: +1-650-319-8930
RTechEmail: rir@cloudflare.com
RTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN

RAbuseHandle: ABUSE2916-ARIN
RAbuseName: Abuse
RAbusePhone: +1-650-319-8930
RAbuseEmail: abuse@cloudflare.com
RAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

Laylax.com Domain Registration and Settings

WHOIS

WHOIS Lookup Tool

Domain Name: LAYLAX.COM
Registry Domain ID: 83662856_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://gmo.jp
Updated Date: 2024-01-16T23:08:23Z
Creation Date: 2002-02-15T09:31:23Z
Registry Expiry Date: 2025-02-15T09:31:23Z
Registrar: GMO Internet Group, Inc. d/b/a Onamae.com
Registrar IANA ID: 49
Registrar Abuse Contact Email: abuse@gmo.jp
Registrar Abuse Contact Phone: +81.337709199
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS01.MUUMUU-DOMAIN.COM
Name Server: DNS02.MUUMUU-DOMAIN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-11-13T03:36:13Z

DNS Records

DNS Lookup Tool

Host	A Record	TTL

Host	MX Record	Priority	TTL

Host	NS Record	TTL

Host	TXT Record	TTL

Laylax.com HTML Check

HTML Validation Tool

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Bad value “” for attribute “alt” on element “input”: Must not be empty.

Bad value “” for attribute “name” on element “input”: Must not be empty.

Bad value “” for attribute “id” on element “li”: An ID must not be the empty string.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Element “dl” is missing a required child element.

Duplicate ID “search”.

Duplicate ID “search_form”.

Duplicate ID “”.

Duplicate ID “130”.

Duplicate ID “56”.

Duplicate ID “74”.

Duplicate ID “75”.

Duplicate ID “76”.

Duplicate ID “77”.

Duplicate ID “78”.

Duplicate ID “79”.

Duplicate ID “155”.

Duplicate ID “154”.

Duplicate ID “80”.

Duplicate ID “81”.

Duplicate ID “7”.

Duplicate ID “133”.

Duplicate ID “8”.

Duplicate ID “146”.

Duplicate ID “142”.

Duplicate ID “24”.

Duplicate ID “11”.

Duplicate ID “9”.

Duplicate ID “30”.

Duplicate ID “44”.

Duplicate ID “45”.

Duplicate ID “153”.

Duplicate ID “48”.

Duplicate ID “47”.

Duplicate ID “46”.

Duplicate ID “49”.

Duplicate ID “50”.

Duplicate ID “26”.

Duplicate ID “152”.

Duplicate ID “148”.

Duplicate ID “150”.

Duplicate ID “29”.

Duplicate ID “134”.

Duplicate ID “135”.

Duplicate ID “138”.

Duplicate ID “141”.

Duplicate ID “139”.

Duplicate ID “140”.

Duplicate ID “137”.

Duplicate ID “136”.

Duplicate ID “34”.

Duplicate ID “52”.

Duplicate ID “53”.

Duplicate ID “54”.

Duplicate ID “55”.

Duplicate ID “19”.

Duplicate ID “20”.

Duplicate ID “132”.

Duplicate ID “143”.

Duplicate ID “36”.

Duplicate ID “35”.

Duplicate ID “57”.

Duplicate ID “58”.

Duplicate ID “59”.

Duplicate ID “61”.

Duplicate ID “62”.

Duplicate ID “60”.

Duplicate ID “64”.

Duplicate ID “65”.

Duplicate ID “67”.

Duplicate ID “68”.

Duplicate ID “63”.

Duplicate ID “66”.

Duplicate ID “69”.

Duplicate ID “70”.

Duplicate ID “72”.

Duplicate ID “71”.

Duplicate ID “73”.

Duplicate ID “145”.

The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.

The “border” attribute on the “table” element is obsolete. Use CSS instead.

Duplicate attribute “style”.

The “center” element is obsolete. Use CSS instead.

Bad value “50%” for attribute “width” on element “img”: Expected a digit but saw “%” instead.

No “p” element in scope but a “p” end tag seen.

Bad value “98%” for attribute “width” on element “img”: Expected a digit but saw “%” instead.

End tag “a” violates nesting rules.

No “strong” element in scope but a “strong” end tag seen.

The “align” attribute on the “td” element is obsolete. Use CSS instead.

Bad value “/user_data/image/top/icon/NEXT GENERATION.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Stray end tag “tbody”.

Bad value “/user_data/image/top/icon/DOT SIGHT_SCOPE.jpg ” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Bad value “/user_data/image/top/icon/SURVIVALGAME WEAR.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Bad value “/user_data/image/top/icon/POUCH SLING.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Bad value “/user_data/image/top/icon/SURVIVALGAME GOODS.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Bad value “/user_data/image/top/icon/OFFICIAL GOODS.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Stray end tag “a”.

Text not allowed in element “ul” in this context.

Element “br” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Element “span” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

No “li” element in scope but a “li” end tag seen.

Stray start tag “script”.

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

The “language” attribute on the “script” element is obsolete. You can safely omit it.

Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.

The first occurrence of ID “search” was here.

The first occurrence of ID “search_form” was here.

The first occurrence of ID “” was here.

The first occurrence of ID “130” was here.

The first occurrence of ID “56” was here.

The first occurrence of ID “74” was here.

The first occurrence of ID “75” was here.

The first occurrence of ID “76” was here.

The first occurrence of ID “77” was here.

The first occurrence of ID “78” was here.

The first occurrence of ID “79” was here.

The first occurrence of ID “155” was here.

The first occurrence of ID “154” was here.

The first occurrence of ID “80” was here.

The first occurrence of ID “81” was here.

The first occurrence of ID “7” was here.

The first occurrence of ID “133” was here.

The first occurrence of ID “8” was here.

The first occurrence of ID “146” was here.

The first occurrence of ID “142” was here.

The first occurrence of ID “24” was here.

The first occurrence of ID “11” was here.

The first occurrence of ID “9” was here.

The first occurrence of ID “30” was here.

The first occurrence of ID “44” was here.

The first occurrence of ID “45” was here.

The first occurrence of ID “153” was here.

The first occurrence of ID “48” was here.

The first occurrence of ID “47” was here.

The first occurrence of ID “46” was here.

The first occurrence of ID “49” was here.

The first occurrence of ID “50” was here.

The first occurrence of ID “26” was here.

The first occurrence of ID “152” was here.

The first occurrence of ID “148” was here.

The first occurrence of ID “150” was here.

The first occurrence of ID “29” was here.

The first occurrence of ID “134” was here.

The first occurrence of ID “135” was here.

The first occurrence of ID “138” was here.

The first occurrence of ID “141” was here.

The first occurrence of ID “139” was here.

The first occurrence of ID “140” was here.

The first occurrence of ID “137” was here.

The first occurrence of ID “136” was here.

The first occurrence of ID “34” was here.

The first occurrence of ID “52” was here.

The first occurrence of ID “53” was here.

The first occurrence of ID “54” was here.

The first occurrence of ID “55” was here.

The first occurrence of ID “19” was here.

The first occurrence of ID “20” was here.

The first occurrence of ID “132” was here.

The first occurrence of ID “143” was here.

The first occurrence of ID “36” was here.

The first occurrence of ID “35” was here.

The first occurrence of ID “57” was here.

The first occurrence of ID “58” was here.

The first occurrence of ID “59” was here.

The first occurrence of ID “61” was here.

The first occurrence of ID “62” was here.

The first occurrence of ID “60” was here.

The first occurrence of ID “64” was here.

The first occurrence of ID “65” was here.

The first occurrence of ID “67” was here.

The first occurrence of ID “68” was here.

The first occurrence of ID “63” was here.

The first occurrence of ID “66” was here.

The first occurrence of ID “69” was here.

The first occurrence of ID “70” was here.

The first occurrence of ID “72” was here.

The first occurrence of ID “71” was here.

The first occurrence of ID “73” was here.

The first occurrence of ID “145” was here.

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Laylax.com Desktop Performance

Last tested: 07/01/2019

Desktop Speed

Optimize images

Leverage browser caching

Enable compression

Reduce server response time

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Prioritize visible content

Minify JavaScript

Minify HTML

Minify CSS

Desktop Resource Breakdown

Total Resources	243
Number of Hosts	4
Static Resources	237
JavaScript Resources	13
CSS Resources	3

Laylax.com Mobile Insights

Last tested: 06/03/2017

Mobile Usability

96%

Size content to viewport

Size tap targets appropriately

Mobile Speed

14%

Optimize images

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Leverage browser caching

Reduce server response time

Minify CSS

Enable compression

Minify HTML

Mobile Resource Breakdown

Total Resources	81
Number of Hosts	8
Static Resources	73
JavaScript Resources	9
CSS Resources	7

Laylax.com Common Typos

www.laylax.com
www.laylax.net
www.laylax.org
www.laylax.info
www.laylax.biz
www.laylax.us
www.laylax.mobi
www.aylax.com
www.laylax.com
www.paylax.com
www.lpaylax.com
www.playlax.com
www.oaylax.com
www.loaylax.com
www.olaylax.com
www.kaylax.com
www.lkaylax.com
www.klaylax.com
www.lylax.com
www.lqylax.com
www.laqylax.com
www.lqaylax.com
www.lwylax.com
www.lawylax.com
www.lwaylax.com
www.lsylax.com
www.lasylax.com
www.lsaylax.com
www.lzylax.com
www.lazylax.com
www.lzaylax.com
www.lalax.com
www.latlax.com
www.laytlax.com
www.latylax.com
www.laglax.com
www.layglax.com
www.lagylax.com
www.lahlax.com
www.layhlax.com
www.lahylax.com
www.laulax.com
www.layulax.com
www.lauylax.com
www.layax.com
www.laypax.com
www.laylpax.com
www.layplax.com
www.layoax.com
www.layloax.com
www.layolax.com
www.laykax.com
www.laylkax.com
www.layklax.com
www.laylx.com
www.laylqx.com
www.laylaqx.com
www.laylqax.com
www.laylwx.com
www.laylawx.com
www.laylwax.com
www.laylsx.com
www.laylasx.com
www.laylsax.com
www.laylzx.com
www.laylazx.com
www.laylzax.com
www.layla.com
www.laylaz.com
www.laylaxz.com
www.laylas.com
www.laylaxs.com
www.laylad.com
www.laylaxd.com
www.layladx.com
www.laylac.com
www.laylaxc.com
www.laylacx.com
www.laylax.con

Laylax.com LayLax(ライラクス)|エアガン・ガスガン・電動ガン・東京マルイカスタム・サバイバルゲーム装備

Laylax.com Overview

Laylax.com Rank Summary

Laylax.com Website Safety

Laylax.com Rank History

Laylax.com Hosting Information

Laylax.com Domain Registration and Settings

Laylax.com HTML Check

Laylax.com Desktop Performance

Laylax.com Mobile Insights

Laylax.com Similar Audits

Laylax.com Common Typos