Skip to content

Hostname

justfly.ge

Last fetched

justfly.ge resolves to 195.54.179.110, announced in 195.54.178.0/23 by Proservice - Proservice LLC in GE. justfly.ge is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · justfly.geRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/justfly.ge

Resolution chain

IPv6 resolution

No AAAA record for justfly.ge is recorded in WhisperGraph.

Attribution

proservice

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for justfly.ge. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
ads.justfly.ge
airticket.justfly.ge
autodiscover.justfly.ge
aviabiletebi.justfly.ge
cpanel.justfly.ge
cpcalendars.justfly.ge
cpcontacts.justfly.ge
flights.justfly.ge
ge.justfly.ge
georgianairways.justfly.ge
hotellist.justfly.ge
hotels.justfly.ge

Showing 12 of 31. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.hostnodes.ge
  • ns2.hostnodes.ge

MX records

  • justfly.ge

SPF policy

  • a: justfly.ge
  • mx: justfly.ge
  • include: reliablemail.org
  • ip: 131.153.16.202
  • ip: 185.139.129.60
  • ip: 185.139.129.70
  • ip: 190.2.142.113
  • ip: 195.54.179.11
  • ip: 195.54.179.110
  • ip: 198.20.108.26
  • ip: 213.136.80.254
  • ip: 217.23.9.200
  • ip: 85.117.32.246
  • ip: 88.198.165.149

Threat-feed evidence

History

Related pages

Pivot from justfly.ge 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: "justfly.ge"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.