Hostname
gira.io
Last fetched
gira.io resolves to 18.219.255.73, announced in 18.216.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. gira.io is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 18.219.255.73
18.216.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.128.181.27
3.128.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.142.120.187
3.136.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.142.243.83
3.136.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.22.118.90
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 85.245.71.75
85.240.0.0/13 · MEO-RESIDENCIAL - MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A. · Cascais, PT
- 85.247.204.138
85.240.0.0/13 · MEO-RESIDENCIAL - MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A. · Amora, PT
- 85.247.204.177
85.240.0.0/13 · MEO-RESIDENCIAL - MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A. · Amora, PT
- 18.191.55.188
18.191.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
IPv6 resolution
No AAAA record for gira.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
| Subdomain |
|---|
| bd.gira.io |
| dev.gira.io |
| ec.gira.io |
| ecdev.gira.io |
| my.gira.io |
| test.gira.io |
| timer.gira.io |
| volley.gira.io |
| volleydev.gira.io |
| www.gira.io |
Showing 10 of 10 subdomains (10 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1.no-ip.com
- ns2.no-ip.com
- ns3.no-ip.com
- ns4.no-ip.com
- ns5.no-ip.com
MX records
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
SPF policy
- include: zoho.com
Threat-feed evidence
History
Related pages
Pivot from gira.io into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "gira.io"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.