Elyager.dev valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | Erik Elyager⎟Frontend Dev. |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 162.243.166.170 |
| Location | North Bergen, New Jersey, United States |
Related Websites
| Site | Rank |
More to Explore
| emendo.com.mx |
| empaquesflexibles.mx |
| empoderar.gob.bo |
| eneri.com.mx |
| endowellness.co.za |
| enmex.com.mx |
| enfermeras-domicilio.com |
| ense.be |
| ephemera-mag.net |
| entrepareja.net |
| tos.nl |
| tvojnotar.sk |
Elyager.dev Valuation
|
US$4,261
Last updated: Jan 27, 2021
Elyager.dev has global traffic rank of 3,979,481. Elyager.dev has an estimated worth of US$ 4,261, based on its estimated Ads revenue. Elyager.dev receives approximately 778 unique visitors each day. Its web server is located in North Bergen, New Jersey, United States, with IP address 162.243.166.170. According to SiteAdvisor, elyager.dev is unknown to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$4,261 |
| Daily Ads Revenue | US$2 |
| Monthly Ads Revenue | US$70 |
| Yearly Ads Revenue | US$852 |
| Daily Unique Visitors | 778 |
| Note: All traffic and earnings values are estimates. | |
Traffic Ranks
| Global Rank | 3,979,481 |
| Delta (90 Days) | 0 |
| Most Popular In Country | N/A |
| Country Rank | N/A |
DNS Records
| Host | Type | TTL | Data |
| elyager.dev | A | 19 | IP: 162.243.166.170 |
| elyager.dev | A | 19 | IP: 104.248.63.248 |
| elyager.dev | AAAA | 19 | IPv6: 2600:1f1c:471:9d01:bd74:a73e:d449:f92c |
| elyager.dev | AAAA | 19 | IPv6: 2604:a880:400:d0:0:0:dff:1 |
| elyager.dev | MX | 3599 | Priority: 30 Target: alt3.gmr-smtp-in.l.google.com. |
| elyager.dev | MX | 3599 | Priority: 20 Target: alt2.gmr-smtp-in.l.google.com. |
| elyager.dev | MX | 3599 | Priority: 10 Target: alt1.gmr-smtp-in.l.google.com. |
| elyager.dev | MX | 3599 | Priority: 5 Target: gmr-smtp-in.l.google.com. |
| elyager.dev | MX | 3599 | Priority: 40 Target: alt4.gmr-smtp-in.l.google.com. |
| elyager.dev | NS | 3599 | Target: dns2.p08.nsone.net. |
| elyager.dev | NS | 3599 | Target: dns3.p08.nsone.net. |
| elyager.dev | NS | 3599 | Target: dns4.p08.nsone.net. |
| elyager.dev | NS | 3599 | Target: dns1.p08.nsone.net. |
| elyager.dev | SOA | 3599 | MNAME: dns1.p08.nsone.net. RNAME: domains+netlify.netlify.com. Serial: 1611733373 Refresh: 43200 Retry: 7200 Expire: 1209600 Minimum TTL: 3600 |
HTTP Headers
HTTP/1.1 301 Moved Permanently Cache-Control: public, max-age=0, must-revalidate Content-Length: 36 Content-Type: text/plain Date: Wed, 27 Jan 2021 22:54:01 GMT Age: 0 Connection: keep-alive Server: Netlify Location: https://elyager.dev/ X-NF-Request-ID: c5b01aeb-863e-456d-9682-ab7b00e96fcf-4154253 HTTP/2 200 cache-control: public, max-age=0, must-revalidate content-type: text/html; charset=UTF-8 date: Wed, 27 Jan 2021 22:54:01 GMT etag: "9bb49b22342f458e912d9f273fac9796-ssl" strict-transport-security: max-age=31536000 age: 0 server: Netlify x-nf-request-id: cac02d68-1418-4080-8528-4c1add9bb6da-70640412 |
Elyager.dev Whois Information
Domain Name: elyager.dev Registry Domain ID: 419833BE2-DEV Registrar WHOIS Server: whois.google.com Registrar URL: domains.google Updated Date: 2020-08-06T20:59:23Z Creation Date: 2020-02-27T09:38:07Z Registry Expiry Date: 2021-02-27T09:38:07Z Registrar: Google LLC. Registrar IANA ID: 895 Registrar Abuse Contact Email: registrar-abuse@google.com Registrar Abuse Contact Phone: +1.8772376466 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: Contact Privacy Inc. Customer 1246565234 Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: ON Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: CA Registrant Phone: REDACTED FOR PRIVACY Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Billing ID: REDACTED FOR PRIVACY Billing Name: REDACTED FOR PRIVACY Billing Organization: REDACTED FOR PRIVACY Billing Street: REDACTED FOR PRIVACY Billing City: REDACTED FOR PRIVACY Billing State/Province: REDACTED FOR PRIVACY Billing Postal Code: REDACTED FOR PRIVACY Billing Country: REDACTED FOR PRIVACY Billing Phone: REDACTED FOR PRIVACY Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: dns1.p08.nsone.net Name Server: dns2.p08.nsone.net Name Server: dns3.p08.nsone.net Name Server: dns4.p08.nsone.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. |