Hostname
aeronaclinic.com
Last fetched
aeronaclinic.com resolves to 108.128.14.160, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. aeronaclinic.com 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
- 108.128.14.160
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 3.248.3.129
3.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.246.107.66
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.247.5.255
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.252.208.228
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.17.153.109
52.16.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.19.81.169
52.18.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.209.174.233
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.210.1.204
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.210.44.69
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.213.112.115
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.31.62.209
52.30.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.50.120.75
52.48.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.171.88.61
54.171.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.195.45.226
54.195.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.75.171.244
54.74.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.76.205.160
54.76.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.77.40.72
54.76.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 63.34.85.15
63.32.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 79.125.67.43
79.125.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for aeronaclinic.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- brigeen peto
- Contact emails
- brigeen.peto@aerona.com, 1053ad93-0f67-45ca-8a22-3138b883ee63@identity-protect.org, bf1a6a62-3f9e-496d-ab19-9d8ac677bdf6@identity-protect.org, bf9b7a0c-933b-4819-bb1c-f89260befc4e@identity-protect.org, ff987704-3078-44a7-8b32-b5403e7f2309@identity-protect.org
Company
- Company
- Aerona Software Ltd.
Technology
Aerona Software Ltd. has been observed using 15 technologies somewhere in its estate. This is observed use, not an exposure finding.
- jQuery · javascript libraries
- Font Awesome · font scripts
- Nginx · web servers
- HSTS · security
- X-Content-Type-Options · web & portal technology
- Amazon Web Services · cloud hosting
- X-XSS-Protection · security
- Slick · javascript libraries
- jQuery UI · javascript libraries
- Amazon ALB · load balancers
- Amazon Route 53 · domain name services
- Java · programming languages
- Select2 · javascript libraries
- DataTables · javascript libraries
- jQuery BlockUI · javascript libraries
Domain portfolio
Parent company's domain: aerona.com (Aerona)
Subdomains
| Subdomain |
|---|
| www.aeronaclinic.com |
Showing 1 of 1 subdomain (1 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
DNSSEC
WhisperGraph records no DNSSEC signature for aeronaclinic.com.
DKIM signing
No DKIM signing vendor is attributed to aeronaclinic.com in WhisperGraph.
Nameservers
- ns-275.awsdns-34.com
- ns-626.awsdns-14.net
- ns-1496.awsdns-59.org
- ns-1844.awsdns-38.co.uk
Threat-feed evidence
History
Related pages
Pivot from aeronaclinic.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.