Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | AgrimData & Servicios, SRL |
Description | N/A |
Keywords | N/A |
WebSite | www.agrimdata.com |
Host IP | 216.239.38.21 |
Location | Mexico City, Mexico City, Mexico |
Site | Rank |
US$20,203
Last updated: Jan 19, 2021
Agrimdata.com has global traffic rank of 4,195,538. Agrimdata.com has an estimated worth of US$ 20,203, based on its estimated Ads revenue. Agrimdata.com receives approximately 738 unique visitors each day. Its web server is located in Mexico City, Mexico City, Mexico, with IP address 216.239.38.21. According to SiteAdvisor, agrimdata.com is safe to visit. |
Purchase/Sale Value | US$20,203 |
Daily Ads Revenue | US$11 |
Monthly Ads Revenue | US$332 |
Yearly Ads Revenue | US$4,040 |
Daily Unique Visitors | 738 |
Note: All traffic and earnings values are estimates. |
Global Rank | 4,195,538 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
agrimdata.com | A | 1799 | IP: 216.239.34.21 |
agrimdata.com | A | 1799 | IP: 216.239.38.21 |
agrimdata.com | A | 1799 | IP: 216.239.36.21 |
agrimdata.com | A | 1799 | IP: 216.239.32.21 |
agrimdata.com | MX | 1218 | Priority: 5 Target: ALT2.ASPMX.L.GOOGLE.com. |
agrimdata.com | MX | 1218 | Priority: 10 Target: ALT3.ASPMX.L.GOOGLE.com. |
agrimdata.com | MX | 1218 | Priority: 1 Target: ASPMX.L.GOOGLE.com. |
agrimdata.com | MX | 1218 | Priority: 5 Target: ALT1.ASPMX.L.GOOGLE.com. |
agrimdata.com | NS | 0 | Target: dns1.name-services.com. |
agrimdata.com | NS | 0 | Target: dns2.name-services.com. |
agrimdata.com | NS | 0 | Target: dns4.name-services.com. |
agrimdata.com | NS | 0 | Target: dns5.name-services.com. |
agrimdata.com | NS | 0 | Target: dns3.name-services.com. |
agrimdata.com | TXT | 1799 | TXT: google-site-verification=6oCb5WddCTcGdTbT2aDR7yK90WWijtmi_Lat8MnAMpc |
agrimdata.com | TXT | 1799 | TXT: google-site-verification=sJc5Cc4ADNhmVCQhCTRnJDQFz-c0yVmefRn9LQyhD_M |
agrimdata.com | SOA | 3599 | MNAME: dns1.name-services.com. RNAME: info.name-services.com. Serial: 1605281475 Refresh: 172800 Retry: 900 Expire: 1814400 Minimum TTL: 3600 |
HTTP/1.1 301 Moved Permanently Location: http://www.agrimdata.com Date: Tue, 19 Jan 2021 00:46:53 GMT Content-Type: text/html; charset=UTF-8 Server: ghs Content-Length: 221 X-XSS-Protection: 0 X-Frame-Options: SAMEORIGIN HTTP/1.1 301 Moved Permanently Content-Type: application/binary Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: Mon, 01 Jan 1990 00:00:00 GMT Date: Tue, 19 Jan 2021 00:46:53 GMT Location: https://www.agrimdata.com/ Server: ESF Content-Length: 0 X-XSS-Protection: 0 X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff HTTP/2 200 content-type: text/html; charset=utf-8 x-frame-options: DENY cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache expires: Mon, 01 Jan 1990 00:00:00 GMT date: Tue, 19 Jan 2021 00:46:53 GMT content-security-policy: base-uri 'self';object-src 'none';report-uri /_/view/cspreport;script-src 'nonce-WteQn3yRW9j3m148OQ1zxA' 'unsafe-inline' 'unsafe-eval';worker-src 'self';frame-ancestors https://google-admin.corp.google.com/ referrer-policy: origin server: ESF x-xss-protection: 0 x-content-type-options: nosniff accept-ranges: none vary: Accept-Encoding |
Domain Name: AGRIMDATA.COM Registry Domain ID: 1908745756_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.enom.com Registrar URL: http://www.enom.com Updated Date: 2020-03-03T10:48:13Z Creation Date: 2015-03-10T10:45:00Z Registry Expiry Date: 2021-03-10T10:45:00Z Registrar: eNom, LLC Registrar IANA ID: 48 Registrar Abuse Contact Email: Registrar Abuse Contact Phone: Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: DNS1.NAME-SERVICES.COM Name Server: DNS2.NAME-SERVICES.COM Name Server: DNS3.NAME-SERVICES.COM Name Server: DNS4.NAME-SERVICES.COM Name Server: DNS5.NAME-SERVICES.COM DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ We're sorry, due to high demand on our WHOIS servers, your request cannot be processed. Please try your request again shortly. |