Skip to content

Hostname

ticket.no

Last fetched

ticket.no resolves to 185.157.223.250, announced in 185.157.220.0/22 by GLESYS - Glesys AB in SE. ticket.no 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 · ticket.noRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/ticket.no

Resolution chain

IPv6 resolution

No AAAA record for ticket.no is recorded in WhisperGraph.

Attribution

glesys

ORIGIN_AS

WHOIS identity

Registrant organisation
ticket feriereiser as
Contact emails
domainadmin@ticket.se

Subdomains

Subdomain
charter.ticket.no
cruise.ticket.no
hotell.ticket.no
hotellguide.ticket.no
jobb.ticket.no
m.ticket.no
nye.ticket.no
restplasser.ticket.no
smetrics.ticket.no
www.ticket.no

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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.dnshost.net
  • ns2.dnshost.net

MX records

  • se.mx1.mailanyone.net
  • se.mx3.mailanyone.net
  • se.mx2.mx25.net
  • se.mx4.mx25.net

SPF policy

  • ip: 213.239.194.92/32
  • include: _relay.amadeus.com
  • include: ticketprivatresor.anpdm.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: spf.cm.puzzel.com
  • include: _spf_v4.staysecuregroup.com
  • include: trustpilotservice.com
  • include: mail.zendesk.com
  • include: spf.mailanyone.net

Threat-feed evidence

History

Related pages

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