Skip to content

Hostname

smartcellular.co.uk

Last fetched

smartcellular.co.uk resolves to 104.26.4.123, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. smartcellular.co.uk 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 · smartcellular.co.ukRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/smartcellular.co.uk

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:123-reg limited t/a 123-reg [tag = 123-reg]
Registrant organisation
identity protect

Subdomains

Subdomain
blog.smartcellular.co.uk
cacheclear.smartcellular.co.uk
cdn.smartcellular.co.uk
clone-stage.smartcellular.co.uk
common-media.smartcellular.co.uk
common-static.smartcellular.co.uk
cpanel.smartcellular.co.uk
dev-sell.smartcellular.co.uk
dev.smartcellular.co.uk
devadmin.smartcellular.co.uk
development.smartcellular.co.uk
email.smartcellular.co.uk

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

  • ashley.ns.cloudflare.com
  • norman.ns.cloudflare.com

MX records

  • mx00.ionos.co.uk
  • mx01.ionos.co.uk

SPF policy

  • include: _spf-eu.ionos.com
  • include: _spf.kundenserver.de
  • include: _spf.perfora.net
  • a: smartcellular.co.uk
  • mx: smartcellular.co.uk
  • a: server.smartcellular.co.uk
  • ip: 103.90.241.60
  • ip: 104.255.220.55
  • ip: 104.255.223.134

Threat-feed evidence

History

Related pages

Pivot from smartcellular.co.uk 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: "smartcellular.co.uk"})-[: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.