trafficsignal.jp Trafficsignal.jp

   
Welcome to trafficsignal.jp

Domain Summary

What is the traffic rank for Trafficsignal.jp?

• Trafficsignal.jp ranks #781,214 globally on HypeStat.

What percent of global Internet users visit Trafficsignal.jp?

• 1.38E-5% of global Internet users visit Trafficsignal.jp

How many people visit Trafficsignal.jp each day?

• Trafficsignal.jp receives approximately 683 visitors and 5,802 page impressions per day.

Which countries does Trafficsignal.jp receive most of its visitors from?

• Trafficsignal.jp is mostly visited by people located in Japan.

How much Trafficsignal.jp can earn?

• Trafficsignal.jp should earn about $2.09/day from advertising revenue.

What is Trafficsignal.jp estimated value?

• Estimated value of Trafficsignal.jp is $2,498.69.

What IP addresses does Trafficsignal.jp resolve to?

• Trafficsignal.jp resolves to the IP addresses 202.208.124.209.

Where are Trafficsignal.jp servers located in?

• Trafficsignal.jp has servers located in Furuichi, Hiroshima, 731-0121, Japan.

trafficsignal.jp Profile

Title:Welcome to trafficsignal.jp
Edit Site Info

What technologies does trafficsignal.jp use?

These are the technologies used at trafficsignal.jp. trafficsignal.jp has a total of 7 technologies installed in 5 different categories.
Web Servers
Apache HTTP Server Apache HTTP Server
Operating Systems
CentOS CentOS
Editors
FrontPage FrontPage
Web Server Extensions
mod_perl mod_perl
OpenSSL OpenSSL
Programming Languages
PHP PHP
Perl Perl

trafficsignal.jp Traffic Analysis

Trafficsignal.jp is ranked #781,214 in the world. This website is viewed by an estimated 683 visitors daily, generating a total of 5.8K pageviews. This equates to about 20.7K monthly visitors. Trafficsignal.jp traffic has increased by 15.41% compared to last month.
Daily Visitors683
81.77%
Monthly Visits20.7K
15.41%
Pages per Visit8.50
1598.79%
Visit duration05:14
1114.29%
Bounce Rate39.92%
75.05%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
683
Monthly Visits:
20,695
Pages per Visit:
8.50
Daily Pageviews:
5,802
Avg. visit duration:
05:14
Bounce rate:
39.92%
Global Reach:
1.38E-5%
Monthly Visits (SEMrush):
21,087
Monthly Unique Visitors (SEMrush):
8,914
Monthly Visits (SimilarWeb):
20,276
HypeRank:
781,214
SEMrush Rank:
12,148,155
SimilarWeb Rank:
781,214
*All traffic values are estimates only.

Traffic sources

Direct:
13.36%
Referral:
11.07%
Search:
48.85%
Social:
13.36%
Paid:
13.36%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

21.3K
DEC
17.9K
JAN
20.7K
FEB

Visitors by country

Country
Users%
 
Japan 100.00%
Last update was 103 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with trafficsignal.jp in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
27,900

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  trafficsignal.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  12,148,155
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  6
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $2.1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $62.7 and annual gross revenue of approximately $762.9. Based on these figures, the site's net worth is estimated at around $2.5K.

How much would trafficsignal.jp make?

Daily Revenue:
$2.09
Monthly Revenue:
$62.70
Yearly Revenue:
$762.85
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 5,802$2.09

Loss of money due to Adblock?

Daily Revenue Loss:
$0.06
Monthly Revenue Loss:
$1.88
Yearly Revenue Loss:
$22.87
Daily Pageviews Blocked:
174
Monthly Pageviews Blocked:
5,222
Yearly Pageviews Blocked:
63,532

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 174$0.06

How much is trafficsignal.jp worth?

Website Value:
$2.5K

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
trafficsignal.jp
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
trafficsignal.jp
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
trafficsignal.jp
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is trafficsignal.jp hosted? ▼

Trafficsignal.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
202.208.124.209
ASN:
AS18144 
ISP:
Energia Communications,Inc. 
Server Location:
Furuichi
Hiroshima, 34
731-0121
Japan, JP
 

Other sites hosted on 202.208.124.209

There are no other sites hosted on this IP

How fast does trafficsignal.jp load? ▼

The average loading time of trafficsignal.jp is 716 ms. The Desktop speed index is 100 and mobile speed index is 99.
Average Load Time:
716 ms

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)143ms 98% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 98% 1% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 1% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)296ms 99% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 99% 0% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)41ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)321ms 99% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 99% 0% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)143ms 98% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 98% 1% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 1% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)296ms 99% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 99% 0% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)41ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)321ms 99% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 99% 0% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Time to Interactive 0.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint 0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow

Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)155ms 98% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 98% 1% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 1% 0% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)360ms 99% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 98% 0% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)301ms 99% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 12% 86% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 86% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)392ms 99% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 99% 0% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)155ms 98% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 98% 1% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 1% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)360ms 98% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 98% 0% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)301ms 12% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 12% 86% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 86% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)392ms 99% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 99% 0% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 0%

Lab Data

Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive 0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors

Does trafficsignal.jp use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on trafficsignal.jp are reduced by %.
trafficsignal.jp does not use compression.
Original size: 3.08 KB
Compressed size: n/a
File reduced by: (%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. trafficsignal.jp has 61 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  61
Safety Confidence:
  3

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. trafficsignal.jp supports HTTPS.
 trafficsignal.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: trafficsignal.jp
Organization:
Location:
Issuer: R11
Valid from: Mar 7 18:10:18 2025 GMT
Valid until: Jun 5 18:10:17 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 trafficsignal.jp does not support HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
Date: Sun, 06 Apr 2025 16:06:42 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_fcgid/2.3.9 PHP/8.1.17 mod_perl/2.0.11 Perl/v5.16.3
Last-Modified: Sun, 01 May 2016 11:53:37 GMT
ETag: "c50-531c686c0aae5"
Accept-Ranges: bytes
Content-Length: 3152
Content-Type: text/html

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 60
Mname ns.furu.org
Rname root.ms.furu.jp
Serial Number 2020121912
Refresh 600
Retry 600
Expire 3600000
Minimum TTL 600
MX trafficsignal.jp 3600
A 202.208.124.209 8
NS ns2.furu.org 86348
NS ns.furu.org 86348

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on February 24, 2002 and will expire on February 28, 2026 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on February 28, 2025.
Domain Created:
2002-02-24
Domain Expires:
2026-02-28
Domain Updated:
2025-02-28
Domain Age:
23 years 4 months 23 days
Domain Owner:
Kaoru Iida
WhoIs:
 

[ JPRS database provides information on network administration. Its use is    ]
[ restricted to network administration purposes. For further information,     ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e'     ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'.                 ]
Domain Information:
[Domain Name]                   TRAFFICSIGNAL.JP

[Registrant]                    Kaoru Iida

[Name Server]                   ns.furu.org
[Name Server]                   ns2.furu.org
[Signing Key]                   

[Created on]                    2002/02/24
[Expires on]                    2026/02/28
[Status]                        Active
[Last Updated]                  2025/03/01 01:05:04 (JST)

Contact Information:
[Name]                          SAKURA internet Inc.
[Email]                         email
[Web Page]                       
[Postal code]                   530-0011
[Postal Address]                Osaka
                                Osaka
                                GRAND GREEN OSAKA North, JAM BASE, 3F 6-38 Ofukacho, Kita-ku
[Phone]                         06-6476-8790
[Fax]