Hostname
giallozafferano.es
Last fetched
giallozafferano.es resolves to 108.131.242.97, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. giallozafferano.es 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.131.242.97
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.132.222.95
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.133.6.63
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.200.57.143
18.200.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.240.56.67
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.243.195.51
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.248.165.59
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.248.235.228
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.251.96.31
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.252.154.1
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.17.231.247
52.16.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.18.255.105
52.18.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.19.244.49
52.18.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.213.251.167
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.215.226.89
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.48.114.209
52.48.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.155.211.174
54.155.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.217.217.147
54.216.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.247.93.221
54.247.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.73.126.15
54.73.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for giallozafferano.es is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for giallozafferano.es. 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.
Company
- Company
- GialloZafferano
- Headquarters
- Spain
Technology
GialloZafferano has been observed using 35 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- Open Graph · content management system
- Google Fonts API · font scripts
- Google Analytics · intelligence and analytics
- Nginx · web servers
- HSTS · security
- HTTP/3 · web & portal technology
- Cloudflare · content delivery network
- Google Tag Manager · tag management
- reCAPTCHA · captcha
- Amazon Web Services · cloud hosting
- Cart Functionality · e-commerce
- Cloudflare CDN · content delivery network
- Cloudflare Bot Management · security
- Swiper · javascript libraries
- PWA · miscellaneous
- Cloudflare Web Optimizations · analytics
- jsDelivr · content delivery network
- Cloudflare Insights · performance
- DoubleClick Floodlight · advertising
- Amazon ALB · load balancers
Domain portfolio
Parent company's domain: giallozafferano.com (GialloZafferano)
Subdomains
| Subdomain |
|---|
| www.giallozafferano.es |
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.
Sample inbound links
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for giallozafferano.es.
DKIM signing
No DKIM signing vendor is attributed to giallozafferano.es in WhisperGraph.
Nameservers
- ns-67.awsdns-08.com
- ns-729.awsdns-27.net
- ns-1311.awsdns-35.org
- ns-1552.awsdns-02.co.uk
Threat-feed evidence
History
Related pages
Pivot from giallozafferano.es 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)
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)
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.