Skip to content

Hostname

clickandsign.eu

Last fetched

clickandsign.eu resolves to 104.18.0.141, announced in 104.28.66.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. clickandsign.eu 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 · clickandsign.euRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/clickandsign.eu

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:register s.p.a.

Subdomains

Subdomain
admin.clickandsign.eu
admintest.clickandsign.eu
api.clickandsign.eu
api6.clickandsign.eu
bedistic.clickandsign.eu
blog.clickandsign.eu
bowizinkpt.clickandsign.eu
caixaenginyers.clickandsign.eu
cuentaswizink.clickandsign.eu
customer.clickandsign.eu
gdpr.clickandsign.eu
klinc.clickandsign.eu

Showing 12 of 19. 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

  • adi.ns.cloudflare.com
  • sid.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • correo01.lleida.net

SPF policy

  • include: spf.getresponse.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: _lleidanetspf1.lleida.net
  • include: _lleidanetspf6.lleida.net

Threat-feed evidence

History

Related pages

Pivot from clickandsign.eu 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: "clickandsign.eu"})-[: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.