whois.handle: AE-DU-20120509
whois.name: Emirates Integrated Telecommunications Company PJSC
whois.cidrs: 5.30.0.0/15 5.32.0.0/17
whois.created: 2012-05-09T00:00:00.000000
whois.updated: 2016-06-22T00:00:00.000000
whois.handle: ORG-DIC1-RIPE
whois.name: Emirates Integrated Telecommunications Company PJSC
whois.address: Dubai International Academic City, Block-9, Floor-7\n502666\nDubai\nUNITED ARAB EMIRATES
whois.handle: EITC2-RIPE
whois.name: EITC Contact Role
whois.handle: BE1098-RIPE
whois.name: Basel Elabed
whois.email: basel.elabed@du.ae
whois.handle: CW1918-RIPE
whois.name: Chanaka Wijekoon
whois.email: chanaka.wijekoon@du.ae
whois.handle: MA14208-RIPE
whois.name: Mohannad AlSayed
whois.email: mohannad.alsayed@du.ae
whois.handle: MD19237-RIPE
whois.name: Mohammed Dakalbab
whois.email: mohammed.dakalbab@du.ae
whois.handle: RR4900-RIPE
whois.name: Rakesh Ravindran
whois.email: rakesh.ravindran@du.ae
services.protocol: HTTP
services.transport_protocol: TCP
services.scan_time: 2025-07-28T00:25:31.346252
services.banner: HTTP/1.1 302 Found
  Date:  <REDACTED>
  X-Frame-Options: SAMEORIGIN
  Content-Security-Policy: frame-ancestors 'self'
  X-XSS-Protection: 1; mode=block
  Location: https://5.30.223.189:443/
  Content-Length: 209
  Content-Type: text/html; charset=iso-8859-1
  
services.path: /
services.endpoint_type: HTTP
services.scan_time: 2025-07-28T00:25:31.346252
services.uri: http://5.30.223.189/
services.protocol: HTTP/1.1
services.status_reason: Found
services.key: Location
services.headers: https://5.30.223.189:443/
services.key: X-Frame-Options
services.headers: SAMEORIGIN
services.key: X-XSS-Protection
services.headers: 1; mode=block
services.key: Content-Length
services.headers: 209
services.key: Content-Security-Policy
services.headers: frame-ancestors 'self'
services.key: Content-Type
services.headers: text/html; charset=iso-8859-1
services.key: Date
services.headers: <REDACTED>
services.html_tags: <title>302 Found</title>
services.body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
  <html><head>
  <title>302 Found</title>
  </head><body>
  <h1>Found</h1>
  <p>The document has moved <a href="https://5.30.223.189:443/">here</a>.</p>
  </body></html>
  
services.body_hash_sha1: sha1:822fd6b11963e43fbb0c82b0bf0ad7bf2a75c1d2
services.supported_versions: HTTP/1.1
services.protocol: HTTP
services.transport_protocol: TCP
services.scan_time: 2025-07-28T08:39:29.684466
services.banner: HTTP/1.1 200 OK
  Date:  <REDACTED>
  X-Frame-Options: SAMEORIGIN
  Content-Security-Policy: frame-ancestors 'self'
  X-XSS-Protection: 1; mode=block
  Strict-Transport-Security: max-age=15552000
  Vary: Accept-encoding
  Cache-Control: no-cache
  Last-Modified: Thu, 29 Jul 2021 23:35:11 GMT
  Accept-Ranges: bytes
  Content-Length: 1214
  Content-Type: text/html
  Content-Encoding: gzip
  
services.version_selected: TLSv1_3
services.cipher_selected: TLS_CHACHA20_POLY1305_SHA256
services.ja4s: t130200_1303_a56c5b993250
services.version: TLSv1_3
services.ja4s: t130200_1303_a56c5b993250
services.version: TLSv1_2
services.ja4s: t120200_c02f_344b4dce5a52
services.version: TLSv1_1
services.ja4s: t110200_c013_344b4dce5a52
services.issuer_dn: O=Fortinet Ltd., CN=FortiGate
services.common_name: FortiGate
services.organization: Fortinet Ltd.
services.subject_dn: O=Fortinet Ltd., CN=FortiGate
services.common_name: FortiGate
services.organization: Fortinet Ltd.
services.scan_time: 2025-07-28T09:23:42.569065
services.path: /ng
services.endpoint_type: HTTP
services.scan_time: 2025-07-28T08:39:29.684466
services.uri: https://5.30.223.189/ng
services.protocol: HTTP/1.1
services.status_reason: OK
services.key: Vary
services.headers: Accept-encoding
services.key: Last-Modified
services.headers: Thu, 29 Jul 2021 23:35:11 GMT
services.key: Accept-Ranges
services.headers: bytes
services.key: Strict-Transport-Security
services.headers: max-age=15552000
services.key: X-Frame-Options
services.headers: SAMEORIGIN
services.key: X-XSS-Protection
services.headers: 1; mode=block
services.key: Content-Type
services.headers: text/html
services.key: Date
services.headers: <REDACTED>
services.key: Content-Encoding
services.headers: gzip
services.key: Content-Length
services.headers: 1214
services.key: Cache-Control
services.headers: no-cache
services.key: Content-Security-Policy
services.headers: frame-ancestors 'self'
services.html_tags: <title ng-bind="::state.model_name + ' - ' + state.hostname"></title> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=8; IE=EDGE"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="apple-itunes-app" content="app-id=1157004084, app-argument={{::host_addr}}">
services.body: <!DOCTYPE html>
  <html lang="en" class="main-app">
      <head>
          <meta charset="UTF-8">
          <meta http-equiv="X-UA-Compatible" content="IE=8; IE=EDGE">
          <meta name="viewport" content="width=device-width, initial-scale=1">
          <meta name="apple-itunes-app" content="app-id=1157004084, app-argument={{::host_addr}}">
          <base href="/ng/">
          <title ng-bind="::state.model_name + ' - ' + state.hostname"></title>
  
          <script>
              function login_redirect() {
                  'use strict';
                  var url = window.location.pathname + window.location.search + window.location.hash;
                  window.location.href = '/logout?redir=' + encodeURIComponent(url);
              }
  
              /**
               * Install a global error handler which can be used to report JS errors back to the
               * FortiGate for inclusion in the httpsd debug log.
               *
               * The global error handler is loaded here because:
               *    - It needs to be set prior to the other scripts loading.
               *    - If it's installed in the context of another script, the error reporting only
               *      applies to script errors in that script file (i.e. fweb_all.js).
               */
              window.onerror = function(message, source, lineno, colno, error) {
                  'use strict';
                  if (fweb && fweb.log && fweb.log.error) {
                      fweb.log.error(error);
                  }
              };
              window.onunhandledrejection = function(rejectionEvent) {
                  'use strict';
                  if (fweb && fweb.log && fweb.log.warn) {
                      fweb.log.warn(`Unhandled promise rejection: "${rejectionEvent.reason}"`);
                  }
              }
          </script>
  
          <!-- If we fail to load any of these scripts then redirect to the login page. Note that
               these checks alone are not sufficient as they may be cached. Similiar logic exists
               in requireJS, $http interceptor, and jQuery.ajax -->
  
          <script src="/1b074eb9f325c1d4a046d3485d1a99d9/ng/ng.bundle.js" onerror="login_redirect()"></script>
      </head>
      <body class="ng-cloak" ng-controller="App">
          <f-header haSync="haSync" currentVdom="currentVdom"
              ng-if="!guestAdmin && !structure.isViewOnly && !structure.isFullscreen"></f-header>
          <f-guest-header ng-if="guestAdmin && !structure.isViewOnly && !structure.isFullscreen"></f-guest-header>
  
          <f-disconnection-notice></f-disconnection-notice>
          <f-shortcuts-help></f-shortcuts-help>
          <f-firmware-upgrade></f-firmware-upgrade>
          <f-terminal></f-terminal>
          <f-release-overview></f-release-overview>
          <f-debugger-capture-notice></f-debugger-capture-notice>
  
          <f-navbar-view-section id="navbar-view-section">
          </f-navbar-view-section>
      </body>
  </html>
  
services.name: https://5.30.223.189/favicon.ico
services.body_hash_sha1: sha1:599f6d90bf3860093b4e3527674ef3c54d26c5aa
services.supported_versions: HTTP/1.1
services.protocol: FORTIGUARD
services.transport_protocol: TCP
services.scan_time: 2025-07-28T07:08:07.772027
[binary data, 17 values, 600 bytes]